[
https://issues.apache.org/jira/browse/HDFS-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189445#comment-13189445
]
Todd Lipcon commented on HDFS-2812:
-----------------------------------
I agree with you in principle, but I'd rather leave it as is for consistency:
{code}
todd@todd-w510:~/svn/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs$ grep -r
nameservice . | wc -l
829
todd@todd-w510:~/svn/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs$ grep -r
nameService . | wc -l
43
{code}
> When becoming active, NN should treat all leases as freshly renewed
> -------------------------------------------------------------------
>
> Key: HDFS-2812
> URL: https://issues.apache.org/jira/browse/HDFS-2812
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Attachments: hdfs-2812.txt, hdfs-2812.txt
>
>
> I haven't seen this yet in practice, but I think the following is a bug:
> - Clients currently only renew leases to the active NN
> - Leases are written into the log when created, but there is no record to
> renew them
> - In Standby state, we don't check leases for expiration. But, when we fail
> over and start the lease monitor, since the leases haven't been renewed, they
> might end up getting incorrectly released.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
