[
https://issues.apache.org/jira/browse/HDFS-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464348#comment-13464348
]
Eli Collins commented on HDFS-3873:
-----------------------------------
Hey Daryn,
With this change we no longer log the exception that caused us to fail to
obtain a token. Intentional?
We now get "cause:java.io.IOException: Unable to obtain remote token" but used
to get..
{noformat}
12/09/26 18:33:10 DEBUG fs.FileSystem: error was
java.io.IOException: Unable to obtain remote token
..
aused by: java.lang.RuntimeException: java.lang.NullPointerException
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1137)
...
{noformat}
> 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
