[jira] [Updated] (WHIRR-636) Default HADOOP_PID_DIR out of sync with CDH4 namenode/datanode service scripts

["Graham Gear (JIRA)" <ji...@apache.org>]

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

Graham Gear updated WHIRR-636:
------------------------------

    Affects Version/s: 0.7.1
    
> Default HADOOP_PID_DIR out of sync with CDH4 namenode/datanode service scripts
> ------------------------------------------------------------------------------
>
>                 Key: WHIRR-636
>                 URL: https://issues.apache.org/jira/browse/WHIRR-636
>             Project: Whirr
>          Issue Type: Bug
>    Affects Versions: 0.7.1
>            Reporter: Graham Gear
>            Priority: Minor
>
> whirr-hadoop-default.properties currently includes:
> hadoop-env.HADOOP_PID_DIR=/var/run/hadoop
> This is at odds with the CDH4 hadoop-hdfs-datanode and hadoop-hdfs-namenode which hardcodes PID file dirs within /var/run/hadoop-hdfs.
> This means the namenode and datanode service scripts do not report correct statuses. Updating HADOOP_PID_DIR to match the System V init scripts resolves the issue.
> This may well be an issue with the System V init scripts, which should refer to the HADOOP_PID_DIR variable rather than the hardcoded value they have today (as per job tracker script etc) - where do think we should address this?

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