[
https://issues.apache.org/jira/browse/HDFS-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195669#comment-14195669
]
Jing Zhao commented on HDFS-7340:
---------------------------------
If we add retry cache support for start/finalize rollingUpgrade, we need to add
rpcId and clientId into the corresponding editlog. This means layout version
may need to be bumped.
Instead, we can make start/finalize rollingUpgrade idempotent.
> rollingUpgrade prepare command does not have retry cache support
> ----------------------------------------------------------------
>
> Key: HDFS-7340
> URL: https://issues.apache.org/jira/browse/HDFS-7340
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.6.0
> Reporter: Arpit Gupta
> Assignee: Jing Zhao
>
> I was running this on a HA cluster with
> dfs.client.test.drop.namenode.response.number set to 1. So the first request
> goes through but the response is dropped. Which then causes another request
> which fails and says a request is already in progress. We should add retry
> cache support for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
