hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (HADOOP-9932) Name node crashes due to improper synchronization in RetryCache
Date Wed, 04 Sep 2013 17:26:54 GMT

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

Kihwal Lee moved HDFS-5162 to HADOOP-9932:
------------------------------------------

    Target Version/s: 2.1.1-beta  (was: 2.1.1-beta)
                 Key: HADOOP-9932  (was: HDFS-5162)
             Project: Hadoop Common  (was: Hadoop HDFS)
    
> Name node crashes due to improper synchronization in RetryCache
> ---------------------------------------------------------------
>
>                 Key: HADOOP-9932
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9932
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Kihwal Lee
>            Priority: Blocker
>
> In LightWeightCache#evictExpiredEntries(), the precondition check can fail. [~patwhitey2007]
ran a HA failover test and it occurred while the SBN was catching up with edits during a transition
to active. This caused NN to terminate.
> Here is my theory: If an RPC handler calls waitForCompletion() and it happens to remove
the head of the queue in get(), it will race with evictExpiredEntries() frrom put().

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message