[
https://issues.apache.org/jira/browse/AMBARI-18569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657000#comment-15657000
]
Hudson commented on AMBARI-18569:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #304 (See
[https://builds.apache.org/job/Ambari-branch-2.5/304/])
AMBARI-18569. Execute topology tasks in parallel by hosts. (Attila (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5eb3bb432bd9570861c3bdd93476a3a2d85e8b76])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/HostRequest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ComponentResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/HostOfferResponse.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/LogicalRequest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostComponentResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/StackEntity.java
> Execute topology tasks in parallel by hosts
> -------------------------------------------
>
> Key: AMBARI-18569
> URL: https://issues.apache.org/jira/browse/AMBARI-18569
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-18569-branch-2.5.patch, AMBARI-18569.patch
>
>
> Currently when a cluster is created using Blueprints,
> {{PersistHostResourcesTask}}, {{RegisterWithConfigGroupTask}},
> {{InstallHostTask}} and {{StartHostTask}} topology tasks are created in this
> order for each host. These tasks are then executed by a single-threaded
> executor {{TopologyManager.executor}} as hosts are being assigned to the
> cluster.
> Since {{TopologyManager}} is singleton, this leads to sequential execution of
> topology tasks on a single thread. The execution of the each individual
> topology task involves db operations under the hood. If for any reason there
> is some latency introduced by the db operations (e.g. the db server is remote
> instead of local) than this latency builds up a considerable delay if there
> are many hosts to execute topology tasks for. Executing the topology tasks
> in parallel would reduce the delay in this case.
> Topology tasks for a host must be executed in order, but tasks that belong to
> different hosts can be executed concurrently. E.g. the
> {{PersistHostResourcesTask}}, {{RegisterWithConfigGroupTask}},
> {{InstallHostTask}} and {{StartHostTask}} topology tasks would be executed
> sequentially by one thread for host1 and by another thread for host2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
