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-761) Failure to process rename operation from edits log due to quota verification
Date Wed, 11 Nov 2009 02:03:27 GMT

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

Hadoop QA commented on HDFS-761:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 834377.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/102/console

This message is automatically generated.

> Failure to process rename operation from edits log due to quota verification
> ----------------------------------------------------------------------------
>                 Key: HDFS-761
>                 URL: https://issues.apache.org/jira/browse/HDFS-761
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.20.2, 0.21.0, 0.22.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.20.2, 0.21.0, 0.22.0
>         Attachments: hdfs-761.1.patch, hdfs-761.1.rel20.patch, hdfs-761.patch, hdfs-761.rel20.patch
> When processing edits log, quota verification is not done and the used quota for directories
is not updated. The update is done at the end of processing edits log. This rule is broken
by change introduced in HDFS-677. This causes namenode from handling rename operation from
edits log due to quota verification failure. Once this happens, namenode does not proceed
edits log any further. This results in check point failure on backup node or secondary namenode.
This also prevents namenode from coming up.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message