You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Robert Nettleton (JIRA)" <ji...@apache.org> on 2015/08/11 16:46:46 UTC

[jira] [Updated] (AMBARI-12720) Blueprint Logical Request stuck in waiting mode during large cluster deployments

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

Robert Nettleton updated AMBARI-12720:
--------------------------------------
    Attachment: AMBARI-12720.patch

Uploaded initial version of patch

> Blueprint Logical Request stuck in waiting mode during large cluster deployments
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-12720
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12720
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>            Priority: Critical
>             Fix For: 2.1.1
>
>         Attachments: AMBARI-12720.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> During Blueprint deployments involving large cluster sizes (50 or more nodes), there is an intermittent failure that occurs in which a logical request never completes, since one or more expected host registrations do not complete, and so the request can not be fully resolved.  This results in the UI showing that the logical request is pending, and the cluster fails to deploy to completion.
> This tends to happen under heavy load with large cluster sizes.  This also tends to happen more frequently when hosts in the cluster are registered with the TopologyManager during the Blueprint configuration phase.  
> This appears to be a concurrency problem with the TopologyManager.
> I'm working on a fix for this, and will be submitting a patch shortly.  



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