Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 18 Jun 2015 20:59:00 +0000 (UTC)
From: "John Speidel (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12838937.1434661083000.113418.1434661140806@Atlassian.JIRA>
In-Reply-To: <JIRA.12838937.1434661083000@Atlassian.JIRA>
References: <JIRA.12838937.1434661083000@Atlassian.JIRA>
 <JIRA.12838937.1434661083748@arcas>
Subject: [jira] [Created] (AMBARI-12009) Occasional concurrent modification
 exception during BP provision of large clusters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

John Speidel created AMBARI-12009:
-------------------------------------

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


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)