hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5371) Let client retry the same NN when "dfs.client.test.drop.namenode.response.number" is enabled
Date Fri, 08 Nov 2013 21:45:17 GMT

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

Jing Zhao updated HDFS-5371:

       Resolution: Fixed
    Fix Version/s: 2.3.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks for the review Suresh! I've committed this to trunk and branch-2.

> Let client retry the same NN when "dfs.client.test.drop.namenode.response.number" is
> --------------------------------------------------------------------------------------------
>                 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

View raw message