ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Jeltema <>
Subject Re: incorrect version displayed after upgrade
Date Thu, 24 Dec 2015 14:39:49 GMT
That did it. Thanks.

> On Dec 24, 2015, at 9:21 AM, Loïc Chanel < <>>
> Hi Brian,
> If this is just a display problem (the version shown by Ambari for the component is not
the right one, and Ambari keeps displaying that the upgrade hasn't finished yet), I think
you can solve it using the final steps of manual upgrade documentation.
> But before doing so, please really insure that all your components have been properly
upgraded by running for example hdfs version on all your hosts.
> Regards,
> Loïc
> System & virtualization engineer
> TO - XaaS Ind - Worldline (Villeurbanne, France)
> 2015-12-24 13:24 GMT+01:00 Brian Jeltema < <>>:
> I just upgraded to Ambari, and then did a rolling upgrade from HDP 2.2 to HDP
> Because of internal name changes, I had to configure my cluster to use customized names
> some nodes, as described in
> It appears that the rolling upgrade does not support this. During the ‘core component’
portion of the upgrade Ambari warned
> about problems upgrading the nodes with the custom names. Ambari claimed that the upgrade
of those
> nodes failed, though by inspection of the directories and links it seems correct. So
I chose to
> continue with the upgrade.
> After finishing the upgrade, All nodes and services appear to be running correctly, and
from the logs it’s clear that
> the HDP 2.3.2 services are running. However, the Ambari ‘Stack and Versions’ page
show HDP 2.2 as ‘Current’,
> and HDP 2.3.2 as “Upgrade: in Process’. Also, the Version column on the Hosts page
shows the incorrect version
> on every node.
> Is there a fix for this?
> Brian

View raw message