ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks
Date Wed, 24 Feb 2016 00:57:18 GMT

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

Alejandro Fernandez updated AMBARI-13424:
-----------------------------------------
    Attachment:     (was: AMBARI-13424.trunk.v3.patch)

> Allow disabling RU/EU PreChecks
> -------------------------------
>
>                 Key: AMBARI-13424
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13424
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.2
>         Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>            Reporter: Robert Ketcherside
>            Assignee: Alejandro Fernandez
>         Attachments: AMBARI-13424.branch-2.2.v3.patch, AMBARI-13424.trunk.v3.patch, Screen
Shot 2016-02-18 at 2.53.07 PM.png, Screen Shot 2016-02-18 at 2.53.24 PM.png, Screen Shot 2016-02-18
at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even if PreChecks
fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called "stack.upgrade.bypass.prechecks"
whose default value is "false"



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

Mime
View raw message