[
https://issues.apache.org/jira/browse/HDFS-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197330#comment-13197330
]
Aaron T. Myers commented on HDFS-2866:
--------------------------------------
bq. Here, I have two nfs-mounted edits directory(shared and one for
fsimage/edits). During failover, edit logs in shared directory is missing a
edit log entry while the edit log entry appears on the other edits directory.
Basically, the two sets of edit logs are off by one txid. The new primary
starts off with the highest txid. However, the standby notices a gap in the
edit logs and cannot proceed further since the standby is using shared edits to
roll forward.
I don't follow how this state could occur. Could you perhaps write a test case
that demonstrates this issue with a minicluster?
> 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