hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Mankude (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2866) Standby does not start up due to a gap in transaction id
Date Wed, 01 Feb 2012 01:06:57 GMT

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

Hari Mankude commented on HDFS-2866:
------------------------------------

Todd's description is correct when there is local edits. We would need to ensure that shared
edit dirs is always first in the list of dirs that is being written. This ensures that if
failover happens when one of the updates is done and the other update is pending, we start
off with the higher txid and this higher txid is available to the standby. 

However, the other issue is to how to get the local dirs back in sync with shared dir now
that they have diverged.
                
> Standby does not start up due to a gap in transaction id
> --------------------------------------------------------
>
>                 Key: HDFS-2866
>                 URL: https://issues.apache.org/jira/browse/HDFS-2866
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Hari Mankude
>            Priority: Critical
>
> Standby notices a gap in the transaction id in the shared.edits directory. The transactions
in dfs.edits.dir does not seem to have the gap. The gap happens during a failover.

--
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

        

Mime
View raw message