[
https://issues.apache.org/jira/browse/HDFS-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584849#comment-13584849
]
Chris Nauroth commented on HDFS-4519:
-------------------------------------
Hi, Jos. I'd like to suggest that we keep the scope of this jira limited to
overriding the jsvc binary, the outfile, and the errfile. Since jsvc is the
expected way to launch a secure data node right now, a change that retires it
may have to be flagged incompatible. The patch I attached here is fairly small
and fully backwards-compatible with the existing behavior.
I'd definitely be curious to see what you have in mind though if you want to
file another jira. Are you thinking that we should drop the jsvc dependency
from Hadoop and push the process management responsibility to the operator, who
can choose to use jsvc or daemontools or whatever other tool is preferred by
that operator?
> 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
