[
https://issues.apache.org/jira/browse/HDFS-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas updated HDFS-761:
---------------------------------
Description: 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.
Environment: (was: 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.)
> 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
>
>
> 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.
