[
https://issues.apache.org/jira/browse/HADOOP-16276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832270#comment-16832270
]
Todd Lipcon commented on HADOOP-16276:
--------------------------------------
hrm. Personally I liked patch 2 better, since as you said, it can be seen as a
compatibility fix. The fix in HADOOP-16289 also seems reasonable, since as
Hrishikesh said, some users may think the new '-cwd /' behavior is more secure
anyway. But, the behavior in the latest patch here is somewhat strange, in that
there's the combination of a passed-in flag _and_ autodetection, which doesn't
seem very intuitive.
> Fix jsvc startup command in hadoop-functions.sh due to jsvc >= 1.0.11 changed
> default current working directory
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-16276
> URL: https://issues.apache.org/jira/browse/HADOOP-16276
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Affects Versions: 3.2.0, 3.1.2
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
> Attachments: HADOOP-16276.001.patch, HADOOP-16276.002.patch,
> HADOOP-16276.003.patch
>
>
> In CDH6, when we bump jsvc from 1.0.10 to 1.1.0 we hit
> *KerberosAuthException: failure to login / LoginException: Unable to obtain
> password from user* due to DAEMON-264 and our
> *dfs.nfs.keytab.file* config uses a relative path. I will probably file
> another jira to issue a warning like *hdfs.keytab not found* before
> KerberosAuthException in this case.
> The solution is to add *-cwd $(pwd)* in function hadoop_start_secure_daemon
> in hadoop-functions.sh but I will have to consider the compatibility with
> older jsvc versions <= 1.0.10. Will post the patch after I tested it.
> Thanks [~tlipcon] for finding the root cause.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
