[ 
https://issues.apache.org/jira/browse/IGNITE-19171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Polovtcev updated IGNITE-19171:
-----------------------------------------
    Description: 
Example failure: 
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleRunner/7122199

The problem is that {{IgnitionManager.init}} sends the Init message to all 
nodes that were passed to it. The first two calls to {{IgnitionManager.init}} 
in the test only send this message to one node, while the third call sends it 
to both nodes. So, there's a race between sending {{ClusterState}} message from 
the CMG leader to the second node (after the CMG group has been created as a 
result of the first init call) and the third explicit {{init}} call, which may 
result in a CMG Raft node being started with a different configuration.

  was:Example failure: 
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleRunner/7122199


> ItClusterInitTest.testDoubleInit is flaky
> -----------------------------------------
>
>                 Key: IGNITE-19171
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19171
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Aleksandr Polovtcev
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> Example failure: 
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleRunner/7122199
> The problem is that {{IgnitionManager.init}} sends the Init message to all 
> nodes that were passed to it. The first two calls to {{IgnitionManager.init}} 
> in the test only send this message to one node, while the third call sends it 
> to both nodes. So, there's a race between sending {{ClusterState}} message 
> from the CMG leader to the second node (after the CMG group has been created 
> as a result of the first init call) and the third explicit {{init}} call, 
> which may result in a CMG Raft node being started with a different 
> configuration.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to