[
https://issues.apache.org/jira/browse/HADOOP-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660135#action_12660135
]
Tsz Wo (Nicholas), SZE commented on HADOOP-4957:
------------------------------------------------
> 1. lease monitor should catch all exceptions log an error and continue to run
> until name-node is running;
> 2. lease monitor should loop until the name-node is FSNamesystem.fsRunning;
If we do the above, it will easily end up an infinite loop when there is a
runtime exception. Consider the case that the oldest lease have a problem
before it gets renew or remove from the queue. Then it will keep sitting on
the top of the queue. The monitor will keep checking the same lease, catching
the same runtime exception again and again.
> Lease monitor should not fail on a live name-node.
> --------------------------------------------------
>
> Key: HADOOP-4957
> URL: https://issues.apache.org/jira/browse/HADOOP-4957
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.3
> Reporter: Konstantin Shvachko
> Assignee: Tsz Wo (Nicholas), SZE
> Fix For: 0.20.0
>
>
> If a runtime exception is thrown inside the lease monitor, as it happened in
> HADOOP-4951, the monitor will die although the name-node will continue to
> run. The problem is that abandoned files will not be garbage collected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
