Wei-Chiu Chuang created HDDS-17398:
--------------------------------------
Summary: SCM should not log ERROR when encountering not leader
exception from datanode
Key: HDDS-17398
URL: https://issues.apache.org/jira/browse/HDDS-17398
Project: Apache Ozone
Issue Type: Bug
Components: SCM
Reporter: Wei-Chiu Chuang
Found quite a lot of this kind of messages in SCM log:
leader failover is common and no hard. It's not an error.
{noformat}
2026-10-22 13:07:43,588 ERROR
[FixedThreadPoolWithAffinityExecutor-0-0]-org.apache.hadoop.hdds.scm.container.IncrementalContainerReportHandler:
Exception while processing ICR for c
ontainer 755121
org.apache.hadoop.hdds.scm.exceptions.SCMException:
org.apache.ratis.protocol.exceptions.NotLeaderException: Server
addac143-8fe5-4fe4-ac31-f206b8d8a0d4@group-3DA1FAA5C2A2 is not t
he leader
af077ffc-b403-4a31-bba9-a33f18d4f71a|rpc:redacted_host0_c09e2f8c-1b2b-57b0-b3af-6cdd49cf8661:9894|admin:|client:|dataStream:|priority:0|startupRole:FOLLOWER
at
org.apache.hadoop.hdds.scm.ha.SCMHAInvocationHandler.translateException(SCMHAInvocationHandler.java:170)
at
org.apache.hadoop.hdds.scm.ha.SCMHAInvocationHandler.invokeRatis(SCMHAInvocationHandler.java:108)
at
org.apache.hadoop.hdds.scm.ha.SCMHAInvocationHandler.invoke(SCMHAInvocationHandler.java:76)
at com.sun.proxy.$Proxy22.updateContainerState(Unknown Source)
at
org.apache.hadoop.hdds.scm.container.ContainerManagerImpl.updateContainerState(ContainerManagerImpl.java:304)
at
org.apache.hadoop.hdds.scm.container.AbstractContainerReportHandler.updateContainerState(AbstractContainerReportHandler.java:319)
at
org.apache.hadoop.hdds.scm.container.AbstractContainerReportHandler.processContainerReplica(AbstractContainerReportHandler.java:121)
at
org.apache.hadoop.hdds.scm.container.IncrementalContainerReportHandler.onMessage(IncrementalContainerReportHandler.java:100)
at
org.apache.hadoop.hdds.scm.container.IncrementalContainerReportHandler.onMessage(IncrementalContainerReportHandler.java:43)
at
org.apache.hadoop.hdds.server.events.FixedThreadPoolWithAffinityExecutor$ContainerReportProcessTask.run(FixedThreadPoolWithAffinityExecutor.java:276)
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.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:829)
Caused by: org.apache.ratis.protocol.exceptions.NotLeaderException: Server
addac143-8fe5-4fe4-ac31-f206b8d8a0d4@group-3DA1FAA5C2A2 is not the leader
af077ffc-b403-4a31-bba9-a33f18d
4f71a|rpc:redacted_host0_c09e2f8c-1b2b-57b0-b3af-6cdd49cf8661:9894|admin:|client:|dataStream:|priority:0|startupRole:FOLLOWER
at
org.apache.ratis.server.impl.RaftServerImpl.generateNotLeaderException(RaftServerImpl.java:744)
at
org.apache.ratis.server.impl.RaftServerImpl.checkLeaderState(RaftServerImpl.java:709)
at
org.apache.ratis.server.impl.RaftServerImpl.submitClientRequestAsync(RaftServerImpl.java:850)
at
org.apache.ratis.server.impl.RaftServerImpl.lambda$null$12(RaftServerImpl.java:831)
at org.apache.ratis.util.JavaUtils.callAsUnchecked(JavaUtils.java:117)
at
org.apache.ratis.server.impl.RaftServerImpl.lambda$executeSubmitClientRequestAsync$13(RaftServerImpl.java:831)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700)
... 3 more
{noformat}
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
