[
https://issues.apache.org/jira/browse/HDFS-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-7340:
----------------------------
Resolution: Fixed
Fix Version/s: 2.6.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Since the change between 000 and 001 patch is only adding a word into the
dfsadmin output (and we do not check the content of this output in the current
unit tests), I committed this patch before waiting for Jenkins again.
> make rollingUpgrade start/finalize idempotent
> ---------------------------------------------
>
> Key: HDFS-7340
> URL: https://issues.apache.org/jira/browse/HDFS-7340
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.4.0
> Reporter: Arpit Gupta
> Assignee: Jing Zhao
> Fix For: 2.6.0
>
> Attachments: HDFS-7340.000.patch, HDFS-7340.001.patch
>
>
> 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)
