You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2014/04/10 20:24:14 UTC
[jira] [Updated] (HDFS-6229) Race condition in failover can cause
RetryCache fail to work
[ https://issues.apache.org/jira/browse/HDFS-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jing Zhao updated HDFS-6229:
----------------------------
Attachment: retrycache-race.patch
The patch can mimic the scenario and cause unit tests in TestRetryCacheWithHA timeout.
> Race condition in failover can cause RetryCache fail to work
> ------------------------------------------------------------
>
> Key: HDFS-6229
> URL: https://issues.apache.org/jira/browse/HDFS-6229
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.1.0-beta
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: retrycache-race.patch
>
>
> Currently when NN failover happens, the old SBN first sets its state to active, then starts the active services (including tailing all the remaining editlog and building a complete retry cache based on the editlog). If a retry request, which has already succeeded in the old ANN (but the client fails to receive the response), comes in between, this retry may still get served by the new ANN but miss the retry cache.
--
This message was sent by Atlassian JIRA
(v6.2#6252)