[jira] [Commented] (AMBARI-12009) Occasional concurrent modification exception during BP provision of large clusters

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on AMBARI-12009:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #2952 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2952/])
AMBARI-12009. Fix occasional ConcurrentModificationException when provisioning (jspeidel: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1b6d7a9e1a5484c56107a2957284392ebbbc8272)
* ambari-server/src/test/java/org/apache/ambari/server/topology/HostGroupInfoTest.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/HostGroupInfo.java


> Occasional concurrent modification exception during BP provision of large clusters
> ----------------------------------------------------------------------------------
>
>                 Key: AMBARI-12009
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12009
>             Project: Ambari
>          Issue Type: Bug
>          Components: blueprints
>    Affects Versions: 2.1.0
>            Reporter: John Speidel
>            Assignee: John Speidel
>             Fix For: 2.1.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When provisioning large clusters via a blueprint, a concurrent modification exception may occur occasionally because the topology manager task executor thread is attempting to create a copy of a collection that is being modified in another thread. Although this exception is caught in the BP provisioning code and retried successfully it is an easy fix and should be fixed in 2.1 to avoid retries which slows down cluster provisioning.



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