ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17559) NN HA enabling failed at 'Stop all Services' step
Date Tue, 05 Jul 2016 12:44:10 GMT

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

Hadoop QA commented on AMBARI-17559:
------------------------------------

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

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

    {color:green}+1 tests included{color}.  The patch appears to include 4 new or modified
test files.

    {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-server.

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

This message is automatically generated.

> NN HA enabling failed at 'Stop all Services' step
> -------------------------------------------------
>
>                 Key: AMBARI-17559
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17559
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17559.patch
>
>
> 1) If a command gets aborted, it remains in "IN_PROGRESS" state on the agent. Agent sends
it in each heartbeat until agent gets restarted.
> 2) Because of an ordering issue in the heartbeat report processing, server sometimes
mismatches command statuses. (If we have COMPLETED command and ABORTED in the same heartbeat,
it may think that completed command was aborted and rejects state change). This situation
was rare previously, but because of the first issue aborted commands come in each Heartbeat.



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

Mime
View raw message