Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sun, 26 Jun 2016 15:27:33 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12983257.1466954817000.1046.1466954853320@Atlassian.JIRA>
In-Reply-To: <JIRA.12983257.1466954817000@Atlassian.JIRA>
References: <JIRA.12983257.1466954817000@Atlassian.JIRA> <JIRA.12983257.1466954817609@arcas>
Subject: [jira] [Created] (AMBARI-17443) Allow commands to specify if they
 should be auto-retried upon failure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 26 Jun 2016 15:27:35 -0000

Sumit Mohanty created AMBARI-17443:
--------------------------------------

             Summary: Allow commands to specify if they should be auto-retried upon failure
                 Key: AMBARI-17443
                 URL: https://issues.apache.org/jira/browse/AMBARI-17443
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.4.0
            Reporter: Sumit Mohanty
            Assignee: Sumit Mohanty
            Priority: Critical
             Fix For: 2.4.0


During cluster creation using a blueprint, the initial INSTALL and START commands are automatically retried by the agent upon failure. This support was added to allow immediate scheduling of commands (as soon as hosts join the cluster) rather than waiting for all hosts to join.

The feature itself is straight forward - if any command failed then agent will automatically retry them for a configurable duration.

Auto retry itself is useful for other commands where user may want some retries before giving up - e.g. Restart commands. Rather than failing immediately agents can try a few more times. Its particularly useful if the start of a service depends on another service which is also being restarted.


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