ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14665) Race condition problem in ServiceComponentHostImpl when provisioning cluster with Blueprint
Date Mon, 18 Jan 2016 20:39:39 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-14665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105799#comment-15105799
] 

Hudson commented on AMBARI-14665:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #4191 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4191/])
AMBARI-14665. Race condition problem in ServiceComponentHostImpl when (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0cbefb3e6ceebea32d71461152aa1f141a8ed5d6])
* ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java


> Race condition problem in ServiceComponentHostImpl when provisioning cluster with Blueprint
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14665
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14665
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>             Fix For: 2.2.1
>
>         Attachments: AMBARI-14665.patch
>
>
> Sometimes when provisioning cluster with Blueprint, there are state inconsistencies between
state and desired_state of components on a given host. Usually desired_state is still INSTALLED
while state is STARTED.
> Analyzing the logs of affected components, the problem seems to be a race condition in
ServiceComponentHostImpl. This is modified by ActionScheduler, HeartBeatMonitor and HostComponentResourceProvider
as well which is used when creating INSTALL and START tasks, modifying desired states.
> ServiceComponentHostImpl state is stored in two entities: HostComponentStateEntity, HostComponentDesiredStateEntity.
Regardless of changes made both entities are merged back to db but only one is fetched from
db before merge.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message