ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez" <>
Subject Re: Review Request 30306: RU - Cluster install did not transition cluster_version to CURRENT because host has only AMS
Date Tue, 27 Jan 2015 04:10:40 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Jan. 27, 2015, 4:10 a.m.)

Review request for Ambari, Jonathan Hurley, Nate Cole, and Yurii Shylov.

Bugs: AMBARI-9340

Repository: ambari


New cluster install through the Install Wizard correctly transitioned all of the host_versions
into CURRENT, but did not propagate the changes to the cluster_version, which stayed stuck
on UPGRADING, because one host only had AMS, so it could not create a host_version record.


  ambari-server/src/main/java/org/apache/ambari/server/agent/ 092f9d54db36686412d7ccaa3318330688cf67cd

  ambari-server/src/main/java/org/apache/ambari/server/state/ b344a052549bb393028a3d60ea9fdb0c2f70fde0

  ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ 220a5af9923444703eab4cff1875f19aeee08742



Testing (updated)

Installed a 3-node cluster with only HDFS, ZK, and AMS. One of the hosts only had the AMS
component. When the install finishes, the other 2 hosts correctly had host_version records
in CURRENT, and the cluster_version was in CURRENT.
After the install finishes, added a 4th node with all 3 components, and it correctly created
a host_version record in the CURRENT state.

This means that the UI needs to be robust enough to handle the case where some hosts don't
have host_version records.

Unit tests are in progress.


Alejandro Fernandez

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