hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4233) NN keeps serving even after no journals started while rolling edit
Date Thu, 29 Nov 2012 21:24:59 GMT

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

Hadoop QA commented on HDFS-4233:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12555405/hdfs-4233.branch-0.23.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3576//console

This message is automatically generated.
                
> 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-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