[
https://issues.apache.org/jira/browse/HDFS-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051032#comment-15051032
]
Kihwal Lee commented on HDFS-7916:
----------------------------------
If the namenode in service successfully received a reportBadBlock request and
then threw exception (i.e. RemoteException), there is no need to retry, thus no
need to unwrap the exception and interpret. But what about SafeModeException?
If the active namenode is in safe mode, do we want it to be retried? If yes, we
might need to interpret the exception.
> 'reportBadBlocks' from datanodes to standby Node BPServiceActor goes for
> infinite loop
> --------------------------------------------------------------------------------------
>
> Key: HDFS-7916
> URL: https://issues.apache.org/jira/browse/HDFS-7916
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Affects Versions: 2.7.0
> Reporter: Vinayakumar B
> Assignee: Rushabh S Shah
> Priority: Critical
> Fix For: 2.7.1
>
> Attachments: HDFS-7916-01.patch, HDFS-7916-1.patch
>
>
> if any badblock found, then BPSA for StandbyNode will go for infinite times
> to report it.
> {noformat}2015-03-11 19:43:41,528 WARN
> org.apache.hadoop.hdfs.server.datanode.DataNode: Failed to report bad block
> BP-1384821822-10.224.54.68-1422634566395:blk_1079544278_5812006 to namenode:
> stobdtserver3/10.224.54.70:18010
> org.apache.hadoop.hdfs.server.datanode.BPServiceActorActionException: Failed
> to report bad block
> BP-1384821822-10.224.54.68-1422634566395:blk_1079544278_5812006 to namenode:
> at
> org.apache.hadoop.hdfs.server.datanode.ReportBadBlockAction.reportTo(ReportBadBlockAction.java:63)
> at
> org.apache.hadoop.hdfs.server.datanode.BPServiceActor.processQueueMessages(BPServiceActor.java:1020)
> at
> org.apache.hadoop.hdfs.server.datanode.BPServiceActor.offerService(BPServiceActor.java:762)
> at
> org.apache.hadoop.hdfs.server.datanode.BPServiceActor.run(BPServiceActor.java:856)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
