[
https://issues.apache.org/jira/browse/IGNITE-9429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607878#comment-16607878
]
Pavel Pereslegin commented on IGNITE-9429:
------------------------------------------
[~agoncharuk], seems we can miss some bugs with catching
IllegalStateException for all datastructures. I see only one problem
in this test - {{G.allGrids()}} returns unordered list, so we should
change:
{code:java}
if (circular)
stopGrid(G.allGrids().get(0).configuration().getIgniteInstanceName());
{code}
to
{code:java}
if (circular)
stopGrid(idx - gridCount());
{code}
This will fix flaky failures and preserves the idea of "circular" node stopping.
> GridCacheReplicatedDataStructuresFailoverSelfTest#testAtomicSequenceConstantTopologyChange
> is flaky
> ---------------------------------------------------------------------------------------------------
>
> Key: IGNITE-9429
> URL: https://issues.apache.org/jira/browse/IGNITE-9429
> Project: Ignite
> Issue Type: Test
> Reporter: Alexey Goncharuk
> Assignee: Alexey Goncharuk
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Test fails with various exception, I see several issues:
> 1) Atomic structure is accessed during a node stop, which leads to
> NodeStoppingException (should be ignored)
> 2) Same race which leads to IllegalStateException: node is stopped
> 3) Invalid atomic integer increment which rarely leads to "Ignite instance
> with the same name has already been started" exception
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
