[
https://issues.apache.org/jira/browse/HADOOP-16276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831833#comment-16831833
]
Hrishikesh Gadre commented on HADOOP-16276:
-------------------------------------------
[~smeng] thanks for adding the environment variable. I personally don't think
that we need to do jsvc version detection and add -cwd param by default since
users (or management software) can always configure this environment variable
based on the jsvc version in their environment. We just need to document this
as part of the release notes. This will make this patch (modulo if block in
patch-003) backwards compatible. what do you think?
> 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]
