Hi,
Alejandro, thanks for your fast response and for the link. On the error we can see which host is not upgraded, in my case a machine called client. But all the packages shows the version 2.5..0.0-1245, anyway also I tried with the command hdp-select set all 2.5.0.0-1245, restarting and refreshing using ambari but nothing changed. Regarding the SQL querys, I am not sure where I should execute those querys. On the master node, I have a PSQL DB with 2 databases called ambari and ambarirca, the DB ambari is empty and the DB ambarirca does not have any tables like repo_version or cluster_version. I only see the following tables: clusterevent hdfsevent job mapreduceevent task taskattempt workflow Thanks, ________________________________ De: Alejandro Fernandez <afernan...@hortonworks.com> Enviado: viernes, 28 de octubre de 2016 20:07:20 Para: user@ambari.apache.org; jml...@hotmail.com Asunto: Re: Ambari, upgrading HDP to 2.5 fail save cluster status Hi Jose, Please take a look at https://community.hortonworks.com/articles/29499/ambari-troubleshooting-a-rolling-or-express-upgrad.html Can you provide this, SELECT repo_version_id, version, display_name FROM repo_version; SELECT repo_version_id, state FROM cluster_version ORDER BY repo_version_id; SELECT repo_version_id, state, COUNT(*) FROM host_version GROUP BY repo_version_id, state ORDER BY repo_version_id, state; SELECT service_name, component_name, version, host_id, upgrade_state FROM hostcomponentstate WHERE version <> '2.5.0.0-1245' AND service_name NOT IN ('AMBARI-METRICS') and component_name NOT IN ('ZKFC', 'KERBEROS_CLIENT') ORDER BY service_name, component_name, host_id; My guess is that at least one host has a host_version record that's not UPGRADED, and hence the cluster_version is not UPGRADED. This will help identify which host and which components are not yet on the newer version. Once you know that, ssh onto that host and run, "hdp-select set all 2.5.0.0-1245". You may then "Pause" the upgrade to regain control of the cluster ops through the UI, then restart the affected components from the Host Details page (if it's a client, then you only need to do "Refresh Configs"). Next, you can "Resume" the upgrade in order to "Finalize". Thanks, Alejandro From: José Manuel Molero <jml...@hotmail.com<mailto:jml...@hotmail.com>> Reply-To: "user@ambari.apache.org<mailto:user@ambari.apache.org>" <user@ambari.apache.org<mailto:user@ambari.apache.org>> Date: Friday, October 28, 2016 at 10:58 AM To: "user@ambari.apache.org<mailto:user@ambari.apache.org>" <user@ambari.apache.org<mailto:user@ambari.apache.org>> Subject: Ambari, upgrading HDP to 2.5 fail save cluster status Hi all, I am using the Hortonworks Hadoop distribution with Ambari. I try to upgrade from HDP 2.4 to 2.5 and I am using Ambari 2.4.1. I try to upgrade using ambari following this guide: https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.1.0/bk_ambari-upgrade/content/upgrading_hdp_stack.html point by point. But always at the end, when the upgrade is finalizing I have always the same error: The following 1 host(s) have not been upgraded to version 2.5.0.0-1245. Please install and upgrade the Stack Version on those hosts and try again. Hosts: client.hadoop But the stack is installed. I check with: hdp-select versions 2.4.0.0-169 2.5.0.0-1245 And all the packages are using the version 2.5.0.0-1245 And ambari is not able to save the status of the cluster. Any help to try to debug would be really helpful. Thanks in advance.
