ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-13032) Automatically Skip Failed Tasks Of Slaves During Upgrade
Date Tue, 08 Sep 2015 13:25:46 GMT
Jonathan Hurley created AMBARI-13032:
----------------------------------------

             Summary: Automatically Skip Failed Tasks Of Slaves During Upgrade
                 Key: AMBARI-13032
                 URL: https://issues.apache.org/jira/browse/AMBARI-13032
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.1.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Critical
             Fix For: 2.1.2


During an upgrade, if any slave component experiences a failure during its restart state then
there should be a way for the rest of the upgrade group to automatically continue despite
the failure. This will prevent the need of administrators to babysit the upgrade process,
especially in cases of larger clusters.

During the creation of the upgrade, an optional parameter should be supplied to the REST endpoint
to accomplish this.

{code:title=POST api/v1/clusters/c1/upgrades}
{
  "Upgrade": {
    "repository_version": "2.3.0.0-2545",
    "skip_failures": true
  }
}
{code}

The various skippable parts of the upgrade can be broken out into distinct request parameters:
- {{skip_failures}} (skips all component failures)
- {{skip_service_check_failures}} (skips all service check failures)

If an upgrade begins without the skip option specified, it can later be added:

{code:title=PUT api/v1/clusters/c1/upgrades/1}
{
  "Upgrade": {
    "skip_failures": true
  }
}
{code}



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

Mime
View raw message