Kirill Sizov created IGNITE-27236:
--------------------------------------

             Summary: Critical system error on Unable to start rebalance 
                 Key: IGNITE-27236
                 URL: https://issues.apache.org/jira/browse/IGNITE-27236
             Project: Ignite
          Issue Type: Improvement
            Reporter:  Kirill Sizov


After the merge of IGNITE-23633 we have started to get occasional exceptions 
like:
{noformat}
[2025-11-28T05:07:33,684][ERROR][%iiimnrt_imnfpr_2%rebalance-scheduler-0][FailureManager]
 Critical system error detected. Will be handled accordingly to configured 
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler 
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=CRITICAL_ERROR, 
failureCtxId=e853191d-0d35-4a68-b907-1969bcca0096]

org.apache.ignite.internal.failure.StackTraceCapturingException: Unable to 
start rebalance [zonePartitionId=20_part_0, term=2]
  at 
org.apache.ignite.internal.failure.FailureManager.process(FailureManager.java:192)
  at 
org.apache.ignite.internal.failure.FailureManager.process(FailureManager.java:169)
  at 
org.apache.ignite.internal.distributionzones.rebalance.ZoneRebalanceRaftGroupEventsListener.maybeRunFailHandler(ZoneRebalanceRaftGroupEventsListener.java:283)
  at 
org.apache.ignite.internal.distributionzones.rebalance.ZoneRebalanceRaftGroupEventsListener.lambda$onLeaderElected$1(ZoneRebalanceRaftGroupEventsListener.java:266)
  at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
  at 
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
  at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
  at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
  at java.base/java.lang.Thread.run(Thread.java:834)
{noformat}

There is a plan to fix it in IGNITE-26085



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

Reply via email to