You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/12/16 15:57:46 UTC

[jira] [Commented] (HADOOP-12650) Document all of the secret env vars

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

Steve Loughran commented on HADOOP-12650:
-----------------------------------------

>From the slider kdiags code, those from UGI alone
{code}
new String[]{
      "HADOOP_JAAS_DEBUG",
      KRB5_CCNAME,
      HADOOP_USER_NAME,
      HADOOP_PROXY_USER,
      HADOOP_TOKEN_FILE_LOCATION,
    }) {
{code}

> Document all of the secret env vars
> -----------------------------------
>
>                 Key: HADOOP-12650
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12650
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 3.0.0
>            Reporter: Allen Wittenauer
>            Priority: Blocker
>
> Over the years, developers have added all kinds of magical environment variables in the Java code without any concern or thought about either a) documenting them or b) whether they are already used by something else.  We need to update at least hadoop-env.sh to contain a list of these env vars so that end users know that they are either private/unsafe and/or how they can be used.
> Just one of many examples: HADOOP_JAAS_DEBUG.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)