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-4233) NN keeps serving even after no journals started while rolling edit
Date Fri, 30 Nov 2012 02:54:00 GMT

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

Kihwal Lee commented on HDFS-4233:
----------------------------------

I decided to go ahead and implement the exit status clearing in HADOOP-9108 for branch-0.23
only. The reason is stated in the jira. With HADOOP-9108, the latest patch in this jira works
without any changes.
                
> NN keeps serving even after no journals started while rolling edit
> ------------------------------------------------------------------
>
>                 Key: HDFS-4233
>                 URL: https://issues.apache.org/jira/browse/HDFS-4233
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 0.23.5
>            Reporter: Kihwal Lee
>            Priority: Blocker
>         Attachments: hdfs-4233.branch-0.23.patch, hdfs-4233.branch-0.23.patch, hdfs-4233-branch-0.23-quick-death.patch
>
>
> We've seen namenode keeps serving even after rollEditLog() failure. Instead of taking
a corrective action or regard this condition as FATAL, it keeps on serving and modifying its
file system state. No logs are written from this point, so if the namenode is restarted, there
will be data loss.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message