Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
3.1.3
-
None
Description
In multi-NameNodes scenario, suppose there are 3 NNs and the 3rd is ANN, and then a client starts rpc with the 1st NN, it will be silent when failover from the 1st NN to the 2nd NN, but when failover from the 2nd NN to the 3rd NN, it prints some unnecessary logs, in some scenarios, these logs will be very numerous:
2019-11-07 11:35:41,577 INFO retry.RetryInvocationHandler: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException): Operation category READ is not supported in state standby. Visit https://s.apache.org/sbnn-error
at org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:98)
at org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:2052)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1459)
...
Attachments
Issue Links
- depends upon
-
HDFS-14963 Add HDFS Client machine caching active namenode index mechanism.
- Patch Available
- is related to
-
HDFS-6440 Support more than 2 NameNodes
- Resolved
-
HDFS-15024 [SBN read] In FailoverOnNetworkExceptionRetry , Number of NameNodes as a condition of calculation of sleep time
- Open
- is superceded by
-
HADOOP-17116 Skip Retry INFO logging on first failover from a proxy
- Resolved