[
https://issues.apache.org/jira/browse/AMBARI-22779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22779:
---------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[branch-2.6|https://github.com/apache/ambari/commit/1fcb0e8a804e5f3c78a9e3ed7c06f79e2ea26a1c]
and
[trunk|https://github.com/apache/ambari/commit/7be21c9148fa0a1cb088d13407974b60dac68b3].
> Cannot scale cluster if Ambari Server restarted since blueprint cluster
> creation
> --------------------------------------------------------------------------------
>
> Key: AMBARI-22779
> URL: https://issues.apache.org/jira/browse/AMBARI-22779
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.0
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Priority: Blocker
> Labels: blueprint, pull-request-available
> Fix For: 3.0.0, 2.6.2
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> STR:
> # Create cluster using blueprint
> # Restart Ambari Server
> # Install Ambari Agent on new host and register with server
> # Add the new host via API request
> # Start Ambari Agent on the new host
> Result: Ambari Server accepts the scale request, but does not proceed to
> install/start components on the new host
> The problem is that AMBARI-22012 fixed a timing/ordering issue by introducing
> an executor, which is started on "cluster configured" event during blueprint
> cluster creation. If Ambari Server is restarted afterwards, the executor will
> stay stopped, hence tasks for scale requests are never executed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
