[
https://issues.apache.org/jira/browse/AMBARI-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007985#comment-15007985
]
Hudson commented on AMBARI-13913:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3847 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3847/])
AMBARI-13913. Express Upgrade: didn't finalize HDFS, improve robustness
(afernandez:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=644d8ba4bb654bd6c8cdaafc4f906bfae7b0a523])
*
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_upgrade.py
*
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
*
ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
*
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
> 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)
