[jira] [Commented] (AMBARI-15063) Metrics monitor fails on restart

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-15063:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12788112/AMBARI-15063.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-metrics/ambari-metrics-timelineservice.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/5397//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5397//console

This message is automatically generated.

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