ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandor Magyari (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-14665) Race condition problem in ServiceComponentHostImpl when provisioning cluster with Blueprint
Date Thu, 14 Jan 2016 11:50:39 GMT
Sandor Magyari created AMBARI-14665:
---------------------------------------

             Summary: 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


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