You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Todd Lipcon (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/19 23:36:40 UTC

[jira] [Resolved] (HDFS-2812) When becoming active, NN should treat all leases as freshly renewed

     [ https://issues.apache.org/jira/browse/HDFS-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon resolved HDFS-2812.
-------------------------------

       Resolution: Fixed
    Fix Version/s: HA branch (HDFS-1623)
     Hadoop Flags: Reviewed

Committed to branch, thanks for review.
                
> 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
>             Fix For: HA branch (HDFS-1623)
>
>         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