[
https://issues.apache.org/jira/browse/HDFS-11027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410452#comment-16410452
]
Hudson commented on HDFS-11027:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13869 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13869/])
HDFS-11027: libbhdfs++: Don't retry if there is an authentication
(james.clampffer: rev b7d9a0f827c0688fa1ebe6b71f0e0a4839d73ea2)
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/rpc/rpc_engine.cc
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/include/hdfspp/status.h
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/common/status.cc
> libhdfs++: Don't retry if there is an authentication failure
> ------------------------------------------------------------
>
> Key: HDFS-11027
> URL: https://issues.apache.org/jira/browse/HDFS-11027
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: James Clampffer
> Assignee: James Clampffer
> Priority: Major
> Attachments: HDFS-11027.HDFS-8707.000.patch,
> HDFS-11027.HDFS-8707.001.patch
>
>
> "Authentication failed" status falls into the general !status.ok() block in
> the HA retry policy so it will keep attempting to failover. If the client
> isn't kerberized, or doesn't have the right ticket it should give up and
> return a meaningful error message (right now it returns a generic bad
> connection failure string).
> Wouldn't hurt to check the FixedDelayRetryPolicy to make sure that doesn't
> also keep attempting to retry in the same way. I suspect it does.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
