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-12720) Blueprint Logical Request stuck in waiting mode during large cluster deployments
Date Fri, 14 Aug 2015 01:30:45 GMT

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

Hudson commented on AMBARI-12720:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #375 (See [https://builds.apache.org/job/Ambari-branch-2.1/375/])
AMBARI-12720. Blueprint Logical Request stuck in waiting mode during large cluster deployments.
(rnettleton) (rnettleton: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=28ca38a0fab7ce0583f8671829f70f3b9ee8765a)
* ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java


> 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.2
>
>   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)

Mime
View raw message