-
Notifications
You must be signed in to change notification settings - Fork 1.9k
IGNITE-14424 #9036
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IGNITE-14424 #9036
Conversation
995a42c to
760df2c
Compare
|
|
||
| /** {@inheritDoc} */ | ||
| @Override public void onDoneAfterTopologyUnlock(GridDhtPartitionsExchangeFuture fut) { | ||
| if (fut.activateCluster() || fut.localJoinExchange()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if the current node joins an inactive cluster?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a node joins an inactive cluster, no PME occurs.
| assertTrue(isReencryptionInProgress(Collections.singleton(cacheName()))); | ||
|
|
||
| node0.cluster().state(ClusterState.INACTIVE); | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stopGrid(GRID_1);
startGrid(GRID_1);
Reproduces the problem I've mentioned above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added this case and fix for it.
(from my point of view, the name of the isReencryptionInProgress method in the test is not entirely correct - this method checks that re-encryption is required, but it doesn’t say whether the re-encryption task is running, I can’t remember why this name was chosen)
…econdary activation. (apache#9036)
Thank you for submitting the pull request to the Apache Ignite.
In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:
The Contribution Checklist
The description explains WHAT and WHY was made instead of HOW.
The following pattern must be used:
IGNITE-XXXX Change summarywhereXXXX- number of JIRA issue.(see the Maintainers list)
the
green visaattached to the JIRA ticket (see TC.Bot: Check PR)Notes
If you need any help, please email dev@ignite.apache.org or ask anу advice on http://asf.slack.com #ignite channel.