You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ambari.apache.org by Brian Jeltema <bd...@gmail.com> on 2015/12/24 13:24:56 UTC
incorrect version displayed after upgrade
I just upgraded to Ambari 2.1.2.1, and then did a rolling upgrade from HDP 2.2 to HDP 2.3.2.
Because of internal name changes, I had to configure my cluster to use customized names for
some nodes, as described in
http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_how_to_customize_the_name_of_a_host.html
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
Re: incorrect version displayed after upgrade
Posted by Brian Jeltema <bd...@gmail.com>.
That did it. Thanks.
> On Dec 24, 2015, at 9:21 AM, Loïc Chanel <loic.chanel@telecomnancy.net <ma...@telecomnancy.net>> wrote:
>
> 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
>
> Loïc CHANEL
> System & virtualization engineer
> TO - XaaS Ind - Worldline (Villeurbanne, France)
>
> 2015-12-24 13:24 GMT+01:00 Brian Jeltema <bdjeltema@gmail.com <ma...@gmail.com>>:
> I just upgraded to Ambari 2.1.2.1, and then did a rolling upgrade from HDP 2.2 to HDP 2.3.2.
>
> Because of internal name changes, I had to configure my cluster to use customized names for
> some nodes, as described in
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_how_to_customize_the_name_of_a_host.html <http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_how_to_customize_the_name_of_a_host.html>
>
> 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
>
Re: incorrect version displayed after upgrade
Posted by Loïc Chanel <lo...@telecomnancy.net>.
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
Loïc CHANEL
System & virtualization engineer
TO - XaaS Ind - Worldline (Villeurbanne, France)
2015-12-24 13:24 GMT+01:00 Brian Jeltema <bd...@gmail.com>:
> I just upgraded to Ambari 2.1.2.1, and then did a rolling upgrade from HDP
> 2.2 to HDP 2.3.2.
>
> Because of internal name changes, I had to configure my cluster to use
> customized names for
> some nodes, as described in
>
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_how_to_customize_the_name_of_a_host.html
>
> 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
Re: incorrect version displayed after upgrade
Posted by Brian Jeltema <bd...@gmail.com>.
Thanks. This is all fixed.
Brian
> On Dec 28, 2015, at 12:56 PM, Alejandro Fernandez <af...@hortonworks.com> wrote:
>
> Hi Artem,
>
> Ambari still believes that the upgrade is in-progress and this will prevent you from changing configs, adding services/hosts.
> Please read https://community.hortonworks.com/articles/2473/rolling-upgrade-express-upgrade-in-ambari.html <https://community.hortonworks.com/articles/2473/rolling-upgrade-express-upgrade-in-ambari.html>
> Especially the SQL queries at the bottom and https://github.com/apache/ambari/tree/branch-2.1.2/contrib/ru_magician <https://github.com/apache/ambari/tree/branch-2.1.2/contrib/ru_magician> for fixing the database.
>
> Thanks,
> Alejandro
>
> From: Artem Ervits <dbist13@gmail.com <ma...@gmail.com>>
> Reply-To: "user@ambari.apache.org <ma...@ambari.apache.org>" <user@ambari.apache.org <ma...@ambari.apache.org>>
> Date: Thursday, December 24, 2015 at 11:17 AM
> To: "user@ambari.apache.org <ma...@ambari.apache.org>" <user@ambari.apache.org <ma...@ambari.apache.org>>
> Subject: Re: incorrect version displayed after upgrade
>
> You can go through each host and finish upgrade.
> On Dec 24, 2015 7:25 AM, "Brian Jeltema" <bdjeltema@gmail.com <ma...@gmail.com>> wrote:
>> I just upgraded to Ambari 2.1.2.1, and then did a rolling upgrade from HDP 2.2 to HDP 2.3.2.
>>
>> Because of internal name changes, I had to configure my cluster to use customized names for
>> some nodes, as described in
>> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_how_to_customize_the_name_of_a_host.html <http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_how_to_customize_the_name_of_a_host.html>
>>
>> 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
Re: incorrect version displayed after upgrade
Posted by Alejandro Fernandez <af...@hortonworks.com>.
Hi Artem,
Ambari still believes that the upgrade is in-progress and this will prevent you from changing configs, adding services/hosts.
Please read https://community.hortonworks.com/articles/2473/rolling-upgrade-express-upgrade-in-ambari.html
Especially the SQL queries at the bottom and https://github.com/apache/ambari/tree/branch-2.1.2/contrib/ru_magician for fixing the database.
Thanks,
Alejandro
From: Artem Ervits <db...@gmail.com>>
Reply-To: "user@ambari.apache.org<ma...@ambari.apache.org>" <us...@ambari.apache.org>>
Date: Thursday, December 24, 2015 at 11:17 AM
To: "user@ambari.apache.org<ma...@ambari.apache.org>" <us...@ambari.apache.org>>
Subject: Re: incorrect version displayed after upgrade
You can go through each host and finish upgrade.
On Dec 24, 2015 7:25 AM, "Brian Jeltema" <bd...@gmail.com>> wrote:
I just upgraded to Ambari 2.1.2.1, and then did a rolling upgrade from HDP 2.2 to HDP 2.3.2.
Because of internal name changes, I had to configure my cluster to use customized names for
some nodes, as described in
http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_how_to_customize_the_name_of_a_host.html
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
Re: incorrect version displayed after upgrade
Posted by Artem Ervits <db...@gmail.com>.
You can go through each host and finish upgrade.
On Dec 24, 2015 7:25 AM, "Brian Jeltema" <bd...@gmail.com> wrote:
> I just upgraded to Ambari 2.1.2.1, and then did a rolling upgrade from HDP
> 2.2 to HDP 2.3.2.
>
> Because of internal name changes, I had to configure my cluster to use
> customized names for
> some nodes, as described in
>
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_how_to_customize_the_name_of_a_host.html
>
> 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