[
https://issues.apache.org/jira/browse/HDFS-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818126#comment-13818126
]
Hudson commented on HDFS-5371:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1604 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1604/])
HDFS-5371. Let client retry the same NN when
dfs.client.test.drop.namenode.response.number is enabled. Contributed by Jing
Zhao. (jing9:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1540197)
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/LossyRetryInvocationHandler.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/retry/RetryPolicies.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> Let client retry the same NN when
> "dfs.client.test.drop.namenode.response.number" is enabled
> --------------------------------------------------------------------------------------------
>
> Key: HDFS-5371
> URL: https://issues.apache.org/jira/browse/HDFS-5371
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ha, test
> Affects Versions: 3.0.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Priority: Minor
> Fix For: 2.3.0
>
> Attachments: HDFS-5371.000.patch
>
>
> Currently when dfs.client.test.drop.namenode.response.number is enabled for
> testing, the client will start failover and try the other NN. But in most of
> the testing cases we do not need to trigger the client failover here since if
> the drop-response number is >1 the next response received from the other NN
> will also be dropped. We can let the client just simply retry the same NN.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
