[jira] [Updated] (IGNITE-22184) ItClusterManagerTest#testJoinInvalidTag is flaky
[ https://issues.apache.org/jira/browse/IGNITE-22184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtsev updated IGNITE-22184: - Fix Version/s: 3.0.0-beta2 > ItClusterManagerTest#testJoinInvalidTag is flaky > > > Key: IGNITE-22184 > URL: https://issues.apache.org/jira/browse/IGNITE-22184 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtsev >Assignee: Aleksandr Polovtsev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Attachments: _Integration_Tests_Module_Cluster_Management_20239.log > > > Looks like there's a race in this test: after the cluster is restarted, the > second node (which does not host the CMG) may be able to connect to the CMG > leader and send a join request after the CMG group is started, but before the > Cluster State is saved (which is done in a separate request). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22184) ItClusterManagerTest#testJoinInvalidTag is flaky
[ https://issues.apache.org/jira/browse/IGNITE-22184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtsev updated IGNITE-22184: - Attachment: _Integration_Tests_Module_Cluster_Management_20239.log > ItClusterManagerTest#testJoinInvalidTag is flaky > > > Key: IGNITE-22184 > URL: https://issues.apache.org/jira/browse/IGNITE-22184 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtsev >Assignee: Aleksandr Polovtsev >Priority: Major > Labels: ignite-3 > Attachments: _Integration_Tests_Module_Cluster_Management_20239.log > > > Looks like there's a race in this test: after the cluster is restarted, the > second node (which does not host the CMG) may be able to connect to the CMG > leader and send a join request after the CMG group is started, but before the > Cluster State is saved (which is done in a separate request). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22184) ItClusterManagerTest#testJoinInvalidTag is flaky
[ https://issues.apache.org/jira/browse/IGNITE-22184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtsev updated IGNITE-22184: - Description: Looks like there's a race in this test: after the cluster is restarted, the second node (which does not host the CMG) may be able to connect to the CMG leader and send a join request after the CMG group is started, but before the Cluster State is saved (which is done in a separate request). > ItClusterManagerTest#testJoinInvalidTag is flaky > > > Key: IGNITE-22184 > URL: https://issues.apache.org/jira/browse/IGNITE-22184 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtsev >Assignee: Aleksandr Polovtsev >Priority: Major > Labels: ignite-3 > > Looks like there's a race in this test: after the cluster is restarted, the > second node (which does not host the CMG) may be able to connect to the CMG > leader and send a join request after the CMG group is started, but before the > Cluster State is saved (which is done in a separate request). -- This message was sent by Atlassian Jira (v8.20.10#820010)
