Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 8 Jun 2015 22:21:00 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12836299.1433802022000.22444.1433802060371@Atlassian.JIRA>
In-Reply-To: <JIRA.12836299.1433802022000@Atlassian.JIRA>
References: <JIRA.12836299.1433802022000@Atlassian.JIRA>
 <JIRA.12836299.1433802022612@arcas>
Subject: [jira] [Created] (AMBARI-11804) Improvements to agent level command
 retry
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sumit Mohanty created AMBARI-11804:
--------------------------------------

             Summary: Improvements to agent level command retry
                 Key: AMBARI-11804
                 URL: https://issues.apache.org/jira/browse/AMBARI-11804
             Project: Ambari
          Issue Type: Bug
          Components: ambari-agent, ambari-server
    Affects Versions: 2.1.0
            Reporter: Sumit Mohanty
            Assignee: Sumit Mohanty
             Fix For: 2.1.0


Proposal:

Introduce three config parameters in {{cluster-env}}

* command_retry_enabled
* command_retry_max_time_in_sec
* commands_to_retry

*command_retry_enabled* - true or false (default is false)
*command_retry_max_time_in_sec* - how long to retry before giving up, default 0, which allows one try
*commands_to_retry* - which commands are eligible for retry, if not set or empty then all commands are eligible, default "START"

By default, retry for service check and custom commands (DECOMMISSION, RESTART, etc) are skipped

As part of this change. properties from ambari.properties file will be removed. So only way to enable is to to provide configs in type cluster-env. So technically it can be disabled/enabled without restarting Ambari.


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