[jira] [Commented] (KNOX-450) WebHDFS HA retry should also handle 'RetriableException' scenarios
[ https://issues.apache.org/jira/browse/KNOX-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14180064#comment-14180064 ] ASF subversion and git services commented on KNOX-450: -- Commit a63961b2015fe9b3466bd530a260d263c2c0bdb1 in knox's branch refs/heads/master from [~kevin.minder] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=a63961b ] KNOX-450: WebHDFS HA retry should also handle RetriableException scenarios WebHDFS HA retry should also handle 'RetriableException' scenarios -- Key: KNOX-450 URL: https://issues.apache.org/jira/browse/KNOX-450 Project: Apache Knox Issue Type: Bug Components: Server Affects Versions: 0.5.0 Reporter: Sumit Gupta Assignee: Sumit Gupta Fix For: 0.5.0 Attachments: KNOX-450.patch When a namenode is starting up and not yet out of safe mode, it may return a RemoteException with the body declaring a RetriableException. Such an exception should be handled by the client by retrying the request. This is currently not handled by Knox's WebHDFS HA feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KNOX-450) WebHDFS HA retry should also handle 'RetriableException' scenarios
[ https://issues.apache.org/jira/browse/KNOX-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14180070#comment-14180070 ] ASF subversion and git services commented on KNOX-450: -- Commit 2154d2d8c9fb8e6e3b65cd76231992d15284d232 in knox's branch refs/heads/v0.5.0 from [~kevin.minder] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=2154d2d ] KNOX-450: WebHDFS HA retry should also handle RetriableException scenarios (cherry picked from commit a63961b2015fe9b3466bd530a260d263c2c0bdb1) WebHDFS HA retry should also handle 'RetriableException' scenarios -- Key: KNOX-450 URL: https://issues.apache.org/jira/browse/KNOX-450 Project: Apache Knox Issue Type: Bug Components: Server Affects Versions: 0.5.0 Reporter: Sumit Gupta Assignee: Sumit Gupta Fix For: 0.5.0 Attachments: KNOX-450.patch When a namenode is starting up and not yet out of safe mode, it may return a RemoteException with the body declaring a RetriableException. Such an exception should be handled by the client by retrying the request. This is currently not handled by Knox's WebHDFS HA feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KNOX-450) WebHDFS HA retry should also handle 'RetriableException' scenarios
[ https://issues.apache.org/jira/browse/KNOX-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14180074#comment-14180074 ] Kevin Minder commented on KNOX-450: --- Commits a63961b2015fe9b3466bd530a260d263c2c0bdb1 and 2154d2d8c9fb8e6e3b65cd76231992d15284d232 contain contribution made by [~sumit.gupta] via KNOX-450.patch. WebHDFS HA retry should also handle 'RetriableException' scenarios -- Key: KNOX-450 URL: https://issues.apache.org/jira/browse/KNOX-450 Project: Apache Knox Issue Type: Bug Components: Server Affects Versions: 0.5.0 Reporter: Sumit Gupta Assignee: Sumit Gupta Fix For: 0.5.0 Attachments: KNOX-450.patch When a namenode is starting up and not yet out of safe mode, it may return a RemoteException with the body declaring a RetriableException. Such an exception should be handled by the client by retrying the request. This is currently not handled by Knox's WebHDFS HA feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
