[
https://issues.apache.org/jira/browse/AMBARI-20440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928270#comment-15928270
]
Sandor Magyari commented on AMBARI-20440:
-----------------------------------------
Committed to trunk & branch-2.5.
> Concurrent odification of HostComponentDesiredState entity results in
> Blueprint based deployment stuck in PENDING state
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-20440
> URL: https://issues.apache.org/jira/browse/AMBARI-20440
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20440.patch
>
>
> If topology tasks are generated in parallel during Blueprint deployment
> (topology.task.creation.parallel=true) sometimes concurrent modification of
> HostComponentDesiredState entity might be modified concurrently which results
> in desiredState remaining in INIT state. As a result HostRoleCommand for
> START topology task is not generated and remains in PENDING state.
> The problem appears when a component is set as restartRequiredAfterRackChange
> in stack definition. In this case when host components are created by
> PersistHostResourcesTask restartRequired is set to true on the same component
> on other hosts, meanwhile InstallHostTask is running which sets the
> desiredState for the same component. As both restartRequired and desiredState
> fields are stored in HostComponentDesiredState entity it could happen then
> when updating restartRequired field desiredState is reverted back to INIT
> state.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
