hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4519) Support override of jsvc binary and log file locations when launching secure datanode.
Date Fri, 22 Feb 2013 00:06:15 GMT

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

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

Hi, Aaron.

I don't see an exact match for this issue, based on the comments I gave above.  I see HDFS-4497,
which upgrades the commons-daemon version dependency on the Java side to resolve a build issue.
 I've been watching and code reviewing that one.  I also found HDFS-2350, an old jira you
filed about how secure data nodes don't print to console.  I reassigned HDFS-2350 to myself,
because the patch I posted here will give us the capability to send jsvc outfile/errfile to
stdout/stderr.

If you see an existing issue that I missed though, please let me know.  Thanks!

                
> 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

Mime
View raw message