[jira] [Updated] (HDFS-4519) Support override of jsvc binary and log file locations when launching secure datanode.

["Chris Nauroth (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated HDFS-4519:
--------------------------------

    Attachment: HDFS-4519-branch-1.1.patch

The attached patch introduces JSVC_HOME, JSVC_OUTFILE, and JSVC_ERRFILE environment variables in the hadoop script on branch-1.  I've successfully tested this change manually on a secure cluster.  I tested overriding to a manually built commons-daemon-1.0.13, and I also tested that the default behavior of using the bundled version of jsvc is still intact.

Here is an example of launching a secure data node using this feature:

{code}
JSVC_HOME=/home/cnauroth/commons-daemon-1.0.13-src/src/native/unix \
  HADOOP_CLASSPATH=/home/cnauroth/commons-daemon-1.0.13-src/dist/commons-daemon-1.0.13.jar \
  HADOOP_USER_CLASSPATH_FIRST=true \
  JSVC_OUTFILE='&1' \
  JSVC_ERRFILE='&2' \
  HADOOP_SECURE_DN_USER=cnauroth \
  sudo -E bin/hadoop datanode
{code}

                
> Support override of jsvc binary and log file locations when launching secure datanode.
> --------------------------------------------------------------------------------------
>
>                 Key: HDFS-4519
>                 URL: https://issues.apache.org/jira/browse/HDFS-4519
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode, scripts
>    Affects Versions: 1.2.0
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HDFS-4519-branch-1.1.patch
>
>
> Currently, builds based on branch-1 bundle a specific version of jsvc pre-built for Linux, and the startup scripts hard-code the location of the output and error files.  Some deployments may prefer to upgrade to a different version of jsvc, independent of the version bundled in Hadoop, and redirect its output elsewhere.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira