Mikhail Efremov created IGNITE-23981:
----------------------------------------
Summary: AssertionError: Illegal state: replica future exists and
was elected as primary, but the future isn't completed
Key: IGNITE-23981
URL: https://issues.apache.org/jira/browse/IGNITE-23981
Project: Ignite
Issue Type: Bug
Reporter: Mikhail Efremov
Assignee: Mikhail Efremov
*Description*
At least at revision {{50c5814}} there are assertion failures on
{{ReplicaStateManager}}'s asserts:
*
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/8697267?showLog=8697253_74949_85.2865&logFilter=debug&logView=flowAware
*
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/8697783?showLog=8697754_264591_85.2877.2880.3097.219152.264591&logFilter=debug&logView=linear
*
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleEngineSqlLogic/8693445
They're demands for investigation.
*Motivation*
There shouldn't be a possible situation where we already elected a primary, but
the replica's future wasn't complete.
*Definition of done*
* the situation was investigated and theoretical scenario of failure is
provided in commentary.
* the possible scenario of non-complete primary replica future is fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
