Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 10 Oct 2016 09:32:21 +0000 (UTC)
From: "Sebastian Toader (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13010965.1476091924000.780521.1476091941939@Atlassian.JIRA>
In-Reply-To: <JIRA.13010965.1476091924000@Atlassian.JIRA>
References: <JIRA.13010965.1476091924000@Atlassian.JIRA> <JIRA.13010965.1476091924655@arcas>
Subject: [jira] [Created] (AMBARI-18560) Add more logging to track what
 condition resulted in skipping agent commands
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 10 Oct 2016 09:32:24 -0000

Sebastian Toader created AMBARI-18560:
-----------------------------------------

             Summary: Add more logging to track what condition resulted in skipping agent commands
                 Key: AMBARI-18560
                 URL: https://issues.apache.org/jira/browse/AMBARI-18560
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
            Reporter: Sebastian Toader
            Assignee: Sebastian Toader
             Fix For: 2.5.0, 2.4.2


Component START/STOP requests received through REST calls may not generate command to be executed by the agents. Currently it's hard track from the INFO level logs if commands were not sent to agents due to legitimate conditions what was the condition that resulted in skipping the creation of commands for agents.


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