[
https://issues.apache.org/jira/browse/HDFS-14792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko resolved HDFS-14792.
----------------------------------------
Fix Version/s: 2.10.1
Resolution: Fixed
This turned out to be related to the same race condition between edits
{{OP_ADD_BLOCK}} and IBRs of HDFS-14941. We do not see any delays in leaving
safemode on StandbyNode after the HDFS-14941 fix.
Closing this as fixed.
> [SBN read] StanbyNode does not come out of safemode while adding new blocks.
> ----------------------------------------------------------------------------
>
> Key: HDFS-14792
> URL: https://issues.apache.org/jira/browse/HDFS-14792
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Affects Versions: 2.10.0
> Reporter: Konstantin Shvachko
> Priority: Major
> Fix For: 2.10.1
>
>
> During startup StandbyNode reports that it needs additional X blocks to reach
> the threshold 1.0000. Where X is changing up and down.
> This is because with fast tailing SBN adds new blocks from edits while DNs
> have not reported replicas yet. Being in SafeMode SBN counts new blocks
> towards the threshold and can stay in SafeMode for a long time.
> By design, the purpose of startup SafeMode is to disallow modifications of
> the namespace and blocks map until all DN replicas are reported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
