[
https://issues.apache.org/jira/browse/HDFS-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449466#comment-13449466
]
Vinay commented on HDFS-3752:
-----------------------------
Hi all,
Sorry for the late reply,
{quote}Maybe we can introduce a new API which BKJM (and QJM) can implement,
which would return the list of available edits ranges, but not necessarily be
available to read them (since these journals don't allow reading from
in-progress edits). That would solve the issue, right? Do you have an idea for
such an API?{quote}
This would be good idea. I think we can implement. I will try this..
{quote}If we couldn't avoid sanity check of the shared storage then I feel
bootstrap can force rollover and then check only till finalized log
segments{quote}
This also seems to work. But only thing is, BOOTSTRAP is kind of readonly
operation. Can we force a log roll from this..?
Any thoughts..?
> 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.1.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
