ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anandha L Ranganathan <analog.s...@gmail.com>
Subject Re: HDP upgrade failed on Finalize Upgrade Pre-Check using ambari.
Date Fri, 20 May 2016 04:17:49 GMT
Thanks Nate. It helps.

I haven't changed anything in the database. I just first tried with
ambari-server restart    After the restart,  I tried again with finalize
pre-check and all the errors are gone.



On Wed, May 18, 2016 at 6:03 PM, Nate Cole <ncole@hortonworks.com> wrote:

> Those steps look correct.  It is always good practice to backup your
> database before trying anything directly against it.
>
>
>
> You should not lose information from an Ambari restart.
>
>
>
> Thanks
>
>
>
> *From: *Anandha L Ranganathan <analog.sony@gmail.com>
> *Reply-To: *"user@ambari.apache.org" <user@ambari.apache.org>
> *Date: *Wednesday, May 18, 2016 at 7:28 PM
> *To: *"user@ambari.apache.org" <user@ambari.apache.org>
> *Cc: *"dev@ambari.apache.org" <dev@ambari.apache.org>
>
> *Subject: *Re: HDP upgrade failed on Finalize Upgrade Pre-Check using
> ambari.
>
>
>
> Thanks Nate for quick reply.
>
> I actually found that in the host_component table , it is still referring
> to old version.
>
> 2
>
> SPARK_CLIENT
>
> 2.2.6.0-2800
>
> 5
>
> INSTALLED
>
> 3
>
> SPARK
>
> NONE
>
> UNKNOWN
>
> 35
>
> 2
>
> SPARK_JOBHISTORYSERVER
>
> 2.2.6.0-2800
>
> 5
>
> STARTED
>
> 6
>
> SPARK
>
> NONE
>
> UNKNOWN
>
> 17
>
> 2
>
> ZOOKEEPER_SERVER
>
> 2.2.6.0-2800
>
> 5
>
> INSTALLED
>
> 154
>
> ZOOKEEPER
>
> NONE
>
> UNSECURED
>
> 78
>
> 2
>
> ZOOKEEPER_SERVER
>
> 2.2.6.0-2800
>
> 5
>
> STARTED
>
> 155
>
> ZOOKEEPER
>
> NONE
>
> UNSECURED
>
> 83
>
>
>
> Can you confirm these are steps I need to take care.
>
>
>
> 1) Update version to latest for the component in the table and commit it.
>
> 2)  Restart the ambari-server.
>
> 3) Continue the upgrade process with retry option.
>
> During the ambari-server restart, just want to confirm will I loose any
> information  or ambari maintains all the state information in the table ?
>
> Thanks
>
> Anand
>
>
>
>
>
> On Wed, May 18, 2016 at 3:04 PM, Nate Cole <ncole@hortonworks.com> wrote:
>
> Are all the services running on the correct version?  If that is the case,
> you can set the actual version in the hostcomponentstate table.  If you
> then restart Ambari, you should be able to retry the step and see if it
> succeeds.
>
>
>
> Thanks
>
> *From: *Anandha L Ranganathan <analog.sony@gmail.com>
> *Reply-To: *"user@ambari.apache.org" <user@ambari.apache.org>
> *Date: *Wednesday, May 18, 2016 at 5:05 PM
> *To: *"user@ambari.apache.org" <user@ambari.apache.org>, "
> dev@ambari.apache.org" <dev@ambari.apache.org>
> *Subject: *Re: HDP upgrade failed on Finalize Upgrade Pre-Check using
> ambari.
>
>
>
> I also verified that in one of the node and it is  pointing to 2.4 version.
>
> [root@usw2dxdpzo01 ~]# ls -lrt /usr/hdp/current/zookeeper-client
> lrwxrwxrwx. 1 root root 30 May 18 15:42 /usr/hdp/current/zookeeper-client
> -> /usr/hdp/2.4.0.0-169/zookeeper
>
>
>
>
>
>
>
> On Wed, May 18, 2016 at 9:44 AM, Anandha L Ranganathan <
> analog.sony@gmail.com> wrote:
>
> Hi,
>
> I created the test cluster and  trying to upgrade HDP 2.4  During the
> upgrade it failed.
>
>
>
> Steps to upgrade the HDP.
>
> Ambari upgrade - ambari-2.1.0 => ambari-2.2.1.0
> HDP upgrade - HDP 2.2.6 => HDP 2.4.0.0
>
>
>
> During the upgrade I had one issues.  forgot to  turn-off the JMX port
> and  during the upgrade I commented that out and it went through fine.    I
> have total 15 instances for this test cluster and it is failed to upgrade 7
> instances.
>
> But in the final steps, "Finalize Upgrade Pre-Check
> <http://localhost:8080/>" it is throwing error. It didn't give any
> information in the log to debug the issue. Also it is not giving an option
> to proceed further. Is there any workaround for this ? The upgrade process
> is completed with 97% and could't proceed further.
>
> 1.  The following components were found to have version mismatches.  Finalize will not
complete successfully:
>
> 2. usw2dxdpgw01: SPARK/SPARK_CLIENT reports 2.2.6.0-2800
>
> 3. usw2dxdpma03: SPARK/SPARK_JOBHISTORYSERVER reports 2.2.6.0-2800
>
> 4. usw2dxdpzo01: ZOOKEEPER/ZOOKEEPER_SERVER reports 2.2.6.0-2800
>
> 5. usw2dxdpzo02: ZOOKEEPER/ZOOKEEPER_SERVER reports 2.2.6.0-2800
>
> 6. usw2dxdpzo03: ZOOKEEPER/ZOOKEEPER_SERVER reports 2.2.6.0-2800
>
> 7. usw2dxdpgw01: ZOOKEEPER/ZOOKEEPER_CLIENT reports 2.2.6.0-2800
>
> 8. usw2dxdpmn01: ZOOKEEPER/ZOOKEEPER_CLIENT reports 2.2.6.0-2800
>
>
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message