You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Karel Vervaeke (JIRA)" <ji...@apache.org> on 2012/08/22 16:58:42 UTC

[jira] [Created] (WHIRR-643) cdh4 init scripts 'status' subcommand broken on HADOOP_PID_DIR mismatch

Karel Vervaeke created WHIRR-643:
------------------------------------

             Summary: cdh4 init scripts 'status' subcommand broken on HADOOP_PID_DIR mismatch
                 Key: WHIRR-643
                 URL: https://issues.apache.org/jira/browse/WHIRR-643
             Project: Whirr
          Issue Type: Bug
         Environment: CDH4
hadoop-hdfs-namenode version 2.0.0+91-1.cdh4.0.1.p0.1~lucid-cdh4.0.1
            Reporter: Karel Vervaeke


I think we should avoid setting HADOOP_PID_DIR when installing cdh4:

/etc/init.d/hadoop-hdfs-namenode start/stop uses $HADOOP_PID_DIR to pick a pidfile.

/etc/init.d/hadoop-hdfs-namenode status uses a hardcoded file ($PIDFILE).

This means the 'status' subcommand is broken when you override HADOOP_PID_DIR in hadoop-env.sh.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (WHIRR-643) cdh4 init scripts 'status' subcommand broken on HADOOP_PID_DIR mismatch

Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WHIRR-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Bayer resolved WHIRR-643.
--------------------------------

    Resolution: Duplicate
    
> cdh4 init scripts 'status' subcommand broken on HADOOP_PID_DIR mismatch
> -----------------------------------------------------------------------
>
>                 Key: WHIRR-643
>                 URL: https://issues.apache.org/jira/browse/WHIRR-643
>             Project: Whirr
>          Issue Type: Bug
>         Environment: CDH4
> hadoop-hdfs-namenode version 2.0.0+91-1.cdh4.0.1.p0.1~lucid-cdh4.0.1
>            Reporter: Karel Vervaeke
>
> I think we should avoid setting HADOOP_PID_DIR when installing cdh4:
> /etc/init.d/hadoop-hdfs-namenode start/stop uses $HADOOP_PID_DIR to pick a pidfile.
> /etc/init.d/hadoop-hdfs-namenode status uses a hardcoded file ($PIDFILE).
> This means the 'status' subcommand is broken when you override HADOOP_PID_DIR in hadoop-env.sh.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira