[ 
https://issues.apache.org/jira/browse/AMBARI-23323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Onischuk updated AMBARI-23323:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk

> Locking configure to single process causes deadlock
> ---------------------------------------------------
>
>                 Key: AMBARI-23323
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23323
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>         Attachments: AMBARI-23323.patch
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 1\. Component1 needs component2 to be started to do configure  
> 2\. Component1 grabs the lock and retries in configure  
> 3\. Component2 cannot grab the lock waiting forever
> This causes variety of timeout errors in different components.  
> Than finally one component will fail with at the end
>     
>     
>     2018-03-22 08:53:01,593 - Trying to acquire a lock on 
> /var/lib/ambari-agent/tmp/link_configs_lock_file
>     



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to