[
https://issues.apache.org/jira/browse/AMBARI-20440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925272#comment-15925272
]
Hadoop QA commented on AMBARI-20440:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858726/AMBARI-20440.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11032//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11032//console
This message is automatically generated.
> 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)
