hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Majercak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-14043) Tolerate corrupted seen_txid file
Date Tue, 06 Nov 2018 00:46:00 GMT

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

Lukas Majercak commented on HDFS-14043:
---------------------------------------

Yes, I ran the TestSaveNamespace in my local trunk version + we ran all the hdfs tests with
this patch applied on top of our internal 2.9 version.

> Tolerate corrupted seen_txid file
> ---------------------------------
>
>                 Key: HDFS-14043
>                 URL: https://issues.apache.org/jira/browse/HDFS-14043
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs, namenode
>    Affects Versions: 2.9.2, 3.1.2, 2.9.3
>            Reporter: Lukas Majercak
>            Assignee: Lukas Majercak
>            Priority: Major
>         Attachments: HDFS-14043.001.patch, HDFS-14043.002.patch, HDFS-14043.003.patch
>
>
> We already tolerate IOExceptions when reading seen_txid file from namenode's dirs. So
we take the maximum txid of all the *readable* namenode dirs. We should extend this to when
the file is corrupted. Currently, PersistentLongFile.readFile throws NumberFormatException
in this case and the whole NN crashes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message