You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/05/30 00:02:18 UTC
[jira] [Commented] (AMBARI-11542) Occasional database deadlock
detected when provisioning cluster via blueprint api
[ 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)