[
https://issues.apache.org/jira/browse/HDFS-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Isaacson updated HDFS-3687:
--------------------------------
Attachment: dn.log
Attaching the trimmed DN log. I noticed that the backtrace happened before the
reboot as well as after.
atm@ theorizes that the bad block report is being sent to both the primary and
the standby NN, is being handled correctly by the primary NN, and is triggering
this error from the secondary NN due to bad block reporting being marked as a
WRITE operation.
> BlockPoolSliceScanner reportBadBlocks fails with Operation category WRITE is
> not supported in state standby
> -----------------------------------------------------------------------------------------------------------
>
> Key: HDFS-3687
> URL: https://issues.apache.org/jira/browse/HDFS-3687
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node
> Affects Versions: 2.0.0-alpha
> Reporter: Andy Isaacson
> Attachments: dn.log
>
>
> Rebooting a DN with a corrupt block results in the blockscanner getting an
> exception while scanning:
> {code}
> 2012-07-19 11:52:09,915 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Reporting bad
> block
> BP-1507505631-172.29.97.196-1337120439433:blk_137178859864142853_112083120
> 2012-07-19 11:52:09,927 WARN org.apache.hadoop.hdfs.server.datanode.DataNode:
> Failed to report bad block
> BP-1507505631-172.29.97.196-1337120439433:blk_137178859864142853_112083120 to
> namenode : Exception
> org.apache.hadoop.ipc.StandbyException: Operation category WRITE is not
> supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1375)
> {code}
> In this case the block got deleted anyways possibly due to being reported to
> the NN by a client, but this might not happen if the file was not recently
> read.
> I'll attach a larger chunk of the DN and NN logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
