Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 5 Jul 2016 11:00:15 +0000 (UTC)
From: "Andrew Onischuk (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12986784.1467716359000.25068.1467716415616@Atlassian.JIRA>
In-Reply-To: <JIRA.12986784.1467716359000@Atlassian.JIRA>
References: <JIRA.12986784.1467716359000@Atlassian.JIRA> <JIRA.12986784.1467716359326@arcas>
Subject: [jira] [Updated] (AMBARI-17559) NN HA enabling failed at 'Stop all
 Services' step
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 05 Jul 2016 11:00:17 -0000


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

Andrew Onischuk updated AMBARI-17559:
-------------------------------------
    Status: Patch Available  (was: Open)

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