[
https://issues.apache.org/jira/browse/HADOOP-16110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767756#comment-16767756
]
Allen Wittenauer commented on HADOOP-16110:
-------------------------------------------
HADOOP_OPTIONAL_TOOLS is one of the big exceptions. It was designed to be a
cluster-wide setting.
The problem is user expectation: a local HADOOP_OPTIONAL_TOOLS setting does not
translate (AFAIK) into the resource manager being able to renew tokens for a
given optional service or those jars being in the classpath on the node
manager. There should probably an error message for settings that don't work,
but that's fairly hard to implement correctly.
> ~/hadoop-env doesn't support HADOOP_OPTIONAL_TOOLS
> --------------------------------------------------
>
> Key: HADOOP-16110
> URL: https://issues.apache.org/jira/browse/HADOOP-16110
> Project: Hadoop Common
> Issue Type: Bug
> Components: bin
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Priority: Minor
>
> if you set {{HADOOP_OPTIONAL_TOOLS}} in ~.hadoop-env, it doesn't get picked
> up because the HADOOP_OPTIONAL_TOOLS expansion takes place in the parse
> process way before {{hadoop_exec_user_hadoopenv}} is invoked.
> Unless I've really misunderstood what ~/.hadoop-env is meant to do "let me
> set hadoop env vars", I'd have expected that tools env var examining (and so:
> loading of optional tools) to take place after
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
