[AMBARI-12322] Installer wizard: cluster deploy failed due to deadlock

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.1.0
• Component/s: ambari-server
• Assignee: Siddharth Wagle
• Reporter: Siddharth Wagle
• Created: 08/Jul/15 00:39
• Updated: 08/Jul/15 20:37
• Resolved: 08/Jul/15 17:42

Description

While creating cluster and its sub resources, UI hanged waiting for API success/failure as found in the analysis.
When manually going over there and going forward UI deletes the cluster instance if found to be existing to begin with. This failed with 500 server error

ambari-server.log

29 Jun 2015 21:28:43,141 ERROR [pool-2-thread-1] AmbariJpaLocalTxnInterceptor:114 - [DETAILED ERROR] Rollback reason:
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource

Error Code: 60
Call: DELETE FROM alert_history WHERE (alert_definition_id = ?)
        bind => [1 parameter bound]
Query: DeleteAllQuery(name="AlertHistoryEntity.removeByDefinitionId" referenceClass=AlertHistoryEntity sql="DELETE FROM alert_history WHERE (alert_definition_id = ?)")
        at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
        at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:900)
        at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:962)

Issue Links

• links to: Review board