[ https://issues.apache.org/jira/browse/IGNITE-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439568#comment-16439568 ]
Alexey Goncharuk commented on IGNITE-8048: ------------------------------------------ Guys, 1) Please remove Hamcrest dependency, it's usage was negatively received by the community and I would abstain of it's usage until there is a consensus 2) Please change MERGE_OF_CONFIG_REQUIRED_MESSAGE to "Failed to join node to the active cluster (the config of the cache '%s" has to be merged which is impossible on active grid). Deactivate grid and retry node join or clean the 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)