hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (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 00:54:56 GMT

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

Todd Lipcon commented on HDFS-2866:
-----------------------------------

One possibility I can imagine is that, if the NN writes a txn group to the local disk and
fsyncs successfully, and then fails before writing to the shared storage, we could have this
scenario.

I think the solution is to make sure that the shared edits dirs always come first in the list
of storage to write to.

Does this sound like the issue you encountered? If not I'll move to a separate ticket.
                
> 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