ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15063) Metrics monitor fails on restart
Date Wed, 17 Feb 2016 02:29:18 GMT

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

Hudson commented on AMBARI-15063:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.2 #346 (See [https://builds.apache.org/job/Ambari-branch-2.2/346/])
AMBARI-15063 : Metrics monitor fails on restart (avijayan) (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2daca3ca63461fc33681efc8d9a3148ed864c00d])
* ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-collector
* ambari-metrics/ambari-metrics-host-monitoring/conf/unix/ambari-metrics-monitor


> Metrics monitor fails on restart
> --------------------------------
>
>                 Key: AMBARI-15063
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15063
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.2.1
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15063.patch
>
>
> PROBLEM
> Metrics Monitor failed to START at install on 1 host. Restart also never worked.
> BUG
> Ambari metrics monitor startup script had a stale pid file with value as 327, and it
used "ps ax -o pid | grep <pid>" to check if the process is running. This returned true
since there was a process with process Id = 3327. Hence, the script always assumed that the
metric monitor process was already running.
> FIX
> Change to use grep exact match (grep -w) while checking for process with process ID.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message