[
https://issues.apache.org/jira/browse/HDFS-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163145#comment-13163145
]
Todd Lipcon commented on HDFS-2634:
-----------------------------------
I also would like to add a safety check in {{initJournalsForWrite}} that makes
sure that under no circumstances do we get overlapping txid ranges. ie prevent
the following from happening:
{code}
$ ls -l /tmp/name-shared/current/
total 4104
-rw-r--r-- 1 todd todd 1048576 2011-12-05 14:41
edits_0000000000000000001-0000000000000000001
-rw-r--r-- 1 todd todd 1048576 2011-12-05 14:45
edits_0000000000000000002-0000000000000000002
-rw-r--r-- 1 todd todd 1048576 2011-12-05 14:58
edits_0000000000000000003-0000000000000000008
-rw-r--r-- 1 todd todd 1048576 2011-12-05 14:59
edits_inprogress_0000000000000000003
{code}
> Standby needs to ingest latest edit logs before transitioning to active`
> ------------------------------------------------------------------------
>
> Key: HDFS-2634
> URL: https://issues.apache.org/jira/browse/HDFS-2634
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
>
> When the standby transitions to active state, it needs to _read_ the latest
> edit logs before it reopens them for write access. Currently, the transition
> calls {{stopStandbyServices}}, which stops the tailer, but doesn't read ahead
> to the very end. This ends up leaving the shared edits dir in an inconsistent
> state where we have overlapping transaction IDs.
--
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
