[
https://issues.apache.org/jira/browse/AMBARI-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549258#comment-13549258
]
Siddharth Wagle commented on AMBARI-1138:
-----------------------------------------
ambari-agent/src/main/python/ambari_agent/StatusCheck.py
Gets the pid files and compares them to a dictionary,
ambari-agent/src/main/python/ambari_agent/servicesToPidNames.dict
The Regular expression for Namenode and other components was too restrictive.
> 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
> 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
