[
https://issues.apache.org/jira/browse/IGNITE-16321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477751#comment-17477751
]
Mirza Aliev edited comment on IGNITE-16321 at 1/18/22, 10:50 AM:
-----------------------------------------------------------------
Root cause of this problem is that there is a gap between user task is applied
to FSM and {{FSMCallerImpl.lastAppliedIndex}} is updated, so we ran
Node#readCommittedUserLog in test, but {{FSMCallerImpl.lastAppliedIndex}} has
not been updated. Note that waiting for the latch in
{{ItNodeTest#sendTestTaskAndWait()}} when tasks are applying doesn't guarantee
that {{FSMCallerImpl.lastAppliedIndex}} will be updated immediately.
was (Author: maliev):
Root cause of this problem is that there is a gap between user task is applied
to FSM and FSMCallerImpl.lastAppliedIndex is updated, so we ran
Node#readCommittedUserLog in test, but FSMCallerImpl.lastAppliedIndex has not
been updated
> ItNodeTest#testChangePeersChaosWithSnapshot is flaky
> ----------------------------------------------------
>
> Key: IGNITE-16321
> URL: https://issues.apache.org/jira/browse/IGNITE-16321
> Project: Ignite
> Issue Type: Bug
> Reporter: Semyon Danilov
> Priority: Major
> Labels: ignite-3
> Attachments: _Integration_Tests_Module_Raft_2696.log.zip
>
>
> Sometimes this test hangs indefinitely with logs like "Node can't do preVote
> as it is not in conf <>".
> See attached TC logs for more information
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
