[
https://issues.apache.org/jira/browse/AMBARI-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-13913:
-----------------------------------------
Description:
For Express Upgrade,
1. We started the NameNodes with "-rollingUpgrade started" but were calling the
wrong finalize command, "-finalizeUpgrade" instead of "-rollingUpgrade
finalize".
2. In HA, if safemode was already on, then the prepare step would fail since
the grep command reported an error.
3. In HA, we now check both NameNodes to come out of safemode. Before, this
would only run on the active one.
was:
For ExpressUpgrade,
1. We started the NameNodes with "-rollingUpgrade started" but were calling the
wrong finalize command, "-finalizeUpgrade" instead of "-rollingUpgrade
finalize".
2. In HA, if safemode was already on, then the prepare step would fail since
the grep command reported an error.
3. In HA, we now check both NameNodes to come out of safemode. Before, this
would only run on the active one.
> Express Upgrade: didn't finalize HDFS, improve robustness for HA
> ----------------------------------------------------------------
>
> Key: AMBARI-13913
> URL: https://issues.apache.org/jira/browse/AMBARI-13913
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0, 2.1.3
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-13913.trunk.patch
>
>
> For Express Upgrade,
> 1. We started the NameNodes with "-rollingUpgrade started" but were calling
> the wrong finalize command, "-finalizeUpgrade" instead of "-rollingUpgrade
> finalize".
> 2. In HA, if safemode was already on, then the prepare step would fail since
> the grep command reported an error.
> 3. In HA, we now check both NameNodes to come out of safemode. Before, this
> would only run on the active one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
