incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-1138) Changing users to non-default values causes servicecomponent live status scripts to report wrong results
Date Fri, 11 Jan 2013 21:12:13 GMT

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

Mahadev konar updated AMBARI-1138:
----------------------------------

    Fix Version/s: 1.2.0
    
> Changing users to non-default values causes servicecomponent live status scripts to report
wrong results
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-1138
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1138
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>            Priority: Blocker
>              Labels: patch
>             Fix For: 1.2.0
>
>         Attachments: patch_3231.txt
>
>
> Changing user to hdfs2 ends up with pid file to end up as hadoop/hdfs2/hadoop-hdfs2-namenode.pid
> This ends up showing namenode as down on the UI even though the process is up.
> Likewise for MR. Probably true for Hbase too.
> Other pid files:
> /var/run/hadoop/mapred2/hadoop-mapred2-jobtracker.pid
> /var/run/hadoop/mapred2/hadoop-mapred2-historyserver.pid
> /var/run/hadoop/hdfs2/hadoop-hdfs2-secondarynamenode.pid 

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