hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3752) BOOTSTRAPSTANDBY for new Standby node will not work just after saveNameSpace at ANN in case of BKJM
Date Fri, 07 Sep 2012 01:26:09 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450249#comment-13450249
] 

Todd Lipcon commented on HDFS-3752:
-----------------------------------

bq. This would be good idea. I think we can implement. I will try this..

Do you think you will get to this in the next couple days? If not, I will have a try at it
-- we need it for QJM as well.

bq. This also seems to work. But only thing is, BOOTSTRAP is kind of readonly operation. Can
we force a log roll from this..?

We used to do this, but then in HDFS-3438 we explicitly removed it so that bootstrap could
complete even when the active is in safemode (or standby state).

If we can't get a proper solution for this easily, we could add an easy workaround flag, like
"bootstrapStandby -skipSharedEditsCheck", since the check here is just to help out the user
and not actually necessary for correct operation.
                
> 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

Mime
View raw message