ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8048) Dynamic indexes are not stored to cache data on node join
Date Thu, 29 Mar 2018 14:58:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419132#comment-16419132
] 

ASF GitHub Bot commented on IGNITE-8048:
----------------------------------------

GitHub user akalash opened a pull request:

    https://github.com/apache/ignite/pull/3719

    IGNITE-8048 merge query entities for dynamic cache during joining node

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8048

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3719.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3719
    
----
commit f80023baa15e67e0ab42fafafa759667176cb32c
Author: Anton Kalashnikov <kaa.dev@...>
Date:   2018-03-29T14:56:51Z

    IGNITE-8048 merge query entities for dynamic cache during joining node

----


> Dynamic indexes are not stored to cache data on node join
> ---------------------------------------------------------
>
>                 Key: IGNITE-8048
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8048
>             Project: Ignite
>          Issue Type: Bug
>          Components: persistence
>    Affects Versions: 2.4
>            Reporter: Alexey Goncharuk
>            Assignee: Anton Kalashnikov
>            Priority: Major
>             Fix For: 2.5
>
>         Attachments: IgniteDynamicIndexRestoreTest.java
>
>
> Consider the following scenario:
> 1) Start nodes, add some data
> 2) Shutdown a node, create a dynamic index
> 3) Shutdown the whole cluster, startup with the absent node, activate from the absent
node
> 4) Since the absent node did not 'see' the create index, index will not be active after
cluster activation
> 5) Update some data in the cluster
> 6) Restart the cluster, but activate from the node which did 'see' the create index
> 7) Attempt to update data. Depending on the updates in (5), this will either hang or
result in an exception



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message