[
https://issues.apache.org/jira/browse/HDFS-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814206#comment-13814206
]
Todd Lipcon commented on HDFS-3752:
-----------------------------------
This might have gotten fixed by HDFS-5080. I don't know anything about BKJM, so
not going to work on this.
> BOOTSTRAPSTANDBY for new Standby node will not work just after saveNameSpace
> at ANN in case of BKJM
> ---------------------------------------------------------------------------------------------------
>
> Key: HDFS-3752
> URL: https://issues.apache.org/jira/browse/HDFS-3752
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha
> Affects Versions: 2.0.0-alpha
> Reporter: Vinay
>
> 1. do {{saveNameSpace}} in ANN node by entering into safemode
> 2. in another new node, install standby NN and do BOOTSTRAPSTANDBY
> 3. Now StandBy NN will not able to copy the fsimage_txid from ANN
> This is because, SNN not able to find the next txid (txid+1) in shared
> storage.
> Just after {{saveNameSpace}} shared storage will have the new logsegment with
> only START_LOG_SEGEMENT edits op.
> and BookKeeper will not be able to read last entry from inprogress ledger.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
