Thank you all for your responses! @Artem Evits
yes, I checked Namenode HA. I also stopped the active Namenode and it switched the secondary Namenode to active.
And there are no Alarms in the Ambari Dashboard
@Sagar Shimpi
I see no upgrade related error in the log. Nothing is logged, when I click on "Perform Upgrade"
@vsharma I'm not sure, if you mean this But the result of this API Call Shows, that it tries to upgrade from 2.2.6 to 2.3.0?!? This is the upgrade I did some months ago {
"href" : "http://srv-hadtest-gw01.fm.db.de:8080/api/v1/clusters/hadtest/upgrades/103?fields=Upgrade&_=1470293691732",
"Upgrade" : {
"cluster_name" : "hadtest",
"create_time" : 1440082089489,
"direction" : "UPGRADE",
"downgrade_allowed" : true,
"end_time" : 1440419026938,
"exclusive" : false,
"from_version" : "2.2.6.0-2800",
"pack" : "upgrade-2.3",
"progress_percent" : 100.0,
"request_context" : "Upgrading to 2.3.0.0-2557",
"request_id" : 103,
"request_status" : "COMPLETED",
"skip_failures" : false,
"skip_service_check_failures" : false,
"start_time" : 1440082089890,
"suspended" : false,
"to_version" : "2.3.0.0-2557",
"type" : "INTERNAL_REQUEST",
"upgrade_type" : "ROLLING"
}
} Ambari shows Version 2.4.0.0 the last entry is, what I added to the ambari database to get the Version 2.4.0.0 displayed in ambari Dashboard. ambari=> select * from cluster_version;
id | repo_version_id | cluster_id | state | start_time | end_time | user_name
-----+-----------------+------------+-----------+---------------+---------------+-----
1 | 1 | 2 | INSTALLED | 1438771088670 | 1438771088683 | _anonymous
51 | 51 | 2 | CURRENT | 1440078962067 | 1440419026925 | admin
101 | 101 | 2 | INSTALLED | 1440078962067 | 1470228028448 | admin
... View more
