hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Templeton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-16276) Fix jsvc startup command in hadoop-functions.sh due to jsvc >= 1.0.11 changed default current working directory
Date Fri, 31 May 2019 16:30:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-16276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853191#comment-16853191
] 

Daniel Templeton commented on HADOOP-16276:
-------------------------------------------

I actually like the auto-detect with an optional override.  We try to do the right thing but
let the user have ultimate control.  The override is important so that management software
can control where the keytabs live.  I think the auto-detect is important to maintain backwards
compatibility.  If someone not using a vendor's tool deploys 3.3 without the auto-detect and
without making the right changes, their deploy will break.

That said, I think the auto-detect is unnecessarily brittle.  Why are we looking for the n-3rd
line instead of grepping for "cwd"?

> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message