hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9533) seen_txid in the shared edits directory is modified during bootstrapping
Date Fri, 12 Feb 2016 16:48:18 GMT

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

Kihwal Lee commented on HDFS-9533:
----------------------------------

I haven't seen it actually creating problems other than our internal monitoring complaining
about it. Since it is rare to do bootstrapStandby to existing HA clusters, we don't have many
data points. 

> seen_txid in the shared edits directory is modified during bootstrapping
> ------------------------------------------------------------------------
>
>                 Key: HDFS-9533
>                 URL: https://issues.apache.org/jira/browse/HDFS-9533
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, namenode
>    Affects Versions: 2.6.0
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>             Fix For: 3.0.0, 2.7.3
>
>         Attachments: HDFS-9533.patch
>
>
> The last known transaction id is stored in the seen_txid file of all known directories
of a NNStorage when starting a new edit segment. However, we have seen a case where it contains
an id that falls in the middle of an edit segment. This was the seen_txid file in the sahred
edits directory.  The active namenode's local storage was containing valid looking seen_txid.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message