Thanks! That helped.
For anyone with a similar problem, the SQL query resulted in the following versions that weren’t “2.2.6.0-2800″.
server1 | AMBARI_METRICS | METRICS_COLLECTOR | UNKNOWN
server4 | AMBARI_METRICS | METRICS_MONITOR | UNKNOWN
server3 | AMBARI_METRICS | METRICS_MONITOR | UNKNOWN
server1 | AMBARI_METRICS | METRICS_MONITOR | UNKNOWN
server2 | AMBARI_METRICS | METRICS_MONITOR | UNKNOWN
server2 | HIVE | MYSQL_SERVER | UNKNOWN
server4 | SQOOP | SQOOP | UNKNOWN
As far as I can tell, HIVE/MYSQL_SERVER and AMBARI_METRICS are expected to be UNKNOWN at this point.
However, SQOOP/SQOOP shouldn’t have been unknown.
Checking my install log, I had removed sqoop from server4 during the install (yum erase sqoop) but had failed to reinstall the package.
Running: yum install “sqoop*” on server 4
resulted in (within a few seconds, I didn’t have to restart Ambari):
– Ambari automatically added “Sqoop” to the left-hand side of the menu. (I didn’t even notice it was missing).
– Ambari automatically updated the database to show:
server4 | SQOOP | SQOOP | 2.2.6.0-2800
and the net result is that the server4 now shows “HDP-2.2.6.0-2800 (Current)” rather than “Upgrading”.
As a possible future enhancement suggestion, it would be nice to expose this somewhere in Ambari as a “problem” rather than hiding it where it can only be found when checking the underlying database. (It’s likely because Sqoop is client-only, rather than a server process that needs to be started, it’s treated differently).
Also, now that server4 has transitioned from Upgrading->Current, the page under “Admin” -> “Stacks and Versions” -> “Versions” now shows “HDP-2.2.6.0-2800″, rather than not showing anything at all. My suspicion is that this may be an Ambari bug; my expectation is that this page should have shown HDP-2.2.6.0-2800 in the “upgrading” state even though not all hosts were “current” on that version.
Thank you!