[
https://issues.apache.org/jira/browse/AMBARI-15482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15482:
-------------------------------------
Status: Patch Available (was: Open)
> Restarting HDFS Before Upgrade Finalizing Does Not Supply the rollingUpgrade
> Flag
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-15482
> URL: https://issues.apache.org/jira/browse/AMBARI-15482
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15482.patch
>
>
> During an upgrade, the HDFS NameNode(s) are restarted with the
> {{-rollingUpgrade}} flag. However, it's possible to get to the end of an
> upgrade and decide to "Finalize Later".
> This allows the cluster to run in the upgraded state before committing to the
> upgrade. Full cluster control is returned via the Ambari web client.
> Administrators can then decide to restart a NameNode. Upon restarting the
> NameNode, it will produce an error that it was not started with the
> {{rollingUpgrade}} flag.
> It seems that as long as an upgrade has not been finalized, the NameNode(s)
> must be started with the {{rollingUpgrade}} to allow them to function
> properly.
> STR:
> - Perform a rolling upgrade from HDP 2.2 to 2.3 (or 2.3 to 2.4); as long as
> there is a major version change.
> - Before finalization, say "Finalize Later". All services should be up and
> green.
> - Now restart a NameNode
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
