Uh oh!
There was an error while loading. Please reload this page.
Fix so dfs.client.failover.max.attempts is respected correctly - #699
Fix so dfs.client.failover.max.attempts is respected correctly#699jbarefoot wants to merge 1 commit into
Conversation
hadoop-yetus
commented
Apr 5, 2019
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
commented
Jul 19, 2019
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
commented
Jul 26, 2019
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
commented
Aug 2, 2019
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
commented
Aug 8, 2019
💔 -1 overall
This message was automatically generated. |
jojochuang
commented
Aug 8, 2019
Is there a jira filed for this? |
jojochuang
commented
Aug 8, 2019
Please follow this doc to file a jira and contribute https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute |
hadoop-yetus
commented
Aug 8, 2019
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
commented
Aug 16, 2019
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
commented
Aug 20, 2019
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
commented
Aug 22, 2019
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
commented
Aug 27, 2019
💔 -1 overall
This message was automatically generated. |
hadoop-yetus
commented
Sep 3, 2019
💔 -1 overall
This message was automatically generated. |
Author: bharathkk <codin.martial@gmail.com> Reviewers: Prateek Maheshwari <pmaheshwari@apache.org>, Shanthoosh Venkatraman <svenkatr@linkedin.com> Closesapache#699 from bharathkk/bug-fix
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
Without this change, you would get incorrect behavior in that you would always have to set
dfs.client.failover.max.attemptsto be +1 greater to have the desired behavior, e.g. if you want it to attempt failover exactly once, you would have to setdfs.client.failover.max.attempts=2.Without this change, if you set
dfs.client.failover.max.attempts=1, to attempt to failover just once time, instead it wouldn't try at all, and you see this log message:Note that the non-failover retries just below this change is correct.