Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 303B71881E for ; Fri, 29 May 2015 22:02:19 +0000 (UTC) Received: (qmail 17895 invoked by uid 500); 29 May 2015 22:02:19 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 17861 invoked by uid 500); 29 May 2015 22:02:19 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 17775 invoked by uid 99); 29 May 2015 22:02:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2015 22:02:19 +0000 Date: Fri, 29 May 2015 22:02:18 +0000 (UTC) From: "Hudson (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-11542) Occasional database deadlock detected when provisioning cluster via blueprint api MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565504#comment-14565504 ] Hudson commented on AMBARI-11542: --------------------------------- SUCCESS: Integrated in Ambari-trunk-Commit #2751 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2751/]) AMBARI-11542. Fix database deadlock that occasionally occurs when provisiong clusters (jspeidel: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5767697ca26d0c3d458dd6cdb6128d20d105c6ca) * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java > Occasional database deadlock detected when provisioning cluster via blueprint api > ---------------------------------------------------------------------------------- > > Key: AMBARI-11542 > URL: https://issues.apache.org/jira/browse/AMBARI-11542 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.1.0 > Reporter: John Speidel > Assignee: John Speidel > Fix For: 2.1.0 > > > When provisioning a cluster via the blueprint api, occasionally a database deadlock is detected. There is retry logic around this code so it doesn't affect the creation of the cluster and a user wouldn't notice this unless they looked at the logs. That being said, this issue involves incorrect transaction demarcation and synchronization and is potentially serious depending on how it is manifested. -- This message was sent by Atlassian JIRA (v6.3.4#6332)