[
https://issues.apache.org/jira/browse/HDFS-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464878#comment-13464878
]
Eli Collins commented on HDFS-3873:
-----------------------------------
I'm saying we should re-introduce the "LOG.debug("error was ", e);" that was
removed below. This debug statement is what gives us the full backtrace (only
if debug is enabled). Make sense?
{code}
- if(LOG.isDebugEnabled()) {
- LOG.debug("error was ", e);
+ } catch (IOException e) {
+ if (e.getCause() instanceof ConnectException) {
+ LOG.warn("Couldn't connect to " + nnHttpUrl +
+ ", assuming security is disabled");
+ return null;
}
{code}
> Hftp assumes security is disabled if token fetch fails
> ------------------------------------------------------
>
> Key: HDFS-3873
> URL: https://issues.apache.org/jira/browse/HDFS-3873
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Affects Versions: 0.23.3, 3.0.0, 2.0.2-alpha
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Fix For: 0.23.3, 2.0.2-alpha
>
> Attachments: HDFS-3873.branch-23.patch, HDFS-3873.patch
>
>
> Hftp ignores all exceptions generated while trying to get a token, based on
> the assumption that it means security is disabled. Debugging problems is
> excruciatingly difficult when security is enabled but something goes wrong.
> Job submissions succeed, but tasks fail because the NN rejects the user as
> unauthenticated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
