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

Chris Nauroth commented on HDFS-4519:
-------------------------------------

trunk already has the capability to set the JSVC_HOME environment variable to 
point at the operator's preferred version of jsvc.  Part of this change will 
back-port support for the JSVC_HOME environment variable to branch-1.  Unlike 
trunk, we will maintain the behavior of defaulting to Hadoop's bundled version 
of jsvc for backwards-compatibility if JSVC_HOME is not specified.  
Additionally, we will introduce JSVC_OUTFILE and JSVC_ERRFILE for redirecting 
the output and error streams of jsvc.

One specific usage of this is to allow use of a new feature added in recent 
jsvc versions to redirect outfile and errfile to stdout and stderr via the 
special arguments '&1' and '&2' respectively.  This feature is not supported in 
the current version bundled in Hadoop, and commons-daemon has stopped providing 
pre-built binary distributions, so we cannot upgrade the bundled version.

                
> 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
>
> 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

Reply via email to