You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Sid Wagle <sw...@hortonworks.com> on 2015/07/08 02:48:29 UTC
Review Request 36287: Installer wizard: cluster deploy failed due to
deadlock
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36287/
-----------------------------------------------------------
Review request for Ambari, Jonathan Hurley, Mahadev Konar, and Myroslav Papirkovskyy.
Bugs: AMBARI-12322
https://issues.apache.org/jira/browse/AMBARI-12322
Repository: ambari
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
{code:title=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)
{code}
Diffs
-----
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertServiceStateListener.java 44f9b50
Diff: https://reviews.apache.org/r/36287/diff/
Testing
-------
Waiting on manual testing results, will post updates based on results.
Thanks,
Sid Wagle
Re: Review Request 36287: Installer wizard: cluster deploy failed due
to deadlock
Posted by Sumit Mohanty <sm...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36287/#review90842
-----------------------------------------------------------
Ship it!
Ship It!
- Sumit Mohanty
On July 8, 2015, 12:48 a.m., Sid Wagle wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/36287/
> -----------------------------------------------------------
>
> (Updated July 8, 2015, 12:48 a.m.)
>
>
> Review request for Ambari, Jonathan Hurley, Mahadev Konar, and Myroslav Papirkovskyy.
>
>
> Bugs: AMBARI-12322
> https://issues.apache.org/jira/browse/AMBARI-12322
>
>
> Repository: ambari
>
>
> 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
>
> {code:title=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)
> {code}
>
>
> Diffs
> -----
>
> ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertServiceStateListener.java 44f9b50
>
> Diff: https://reviews.apache.org/r/36287/diff/
>
>
> Testing
> -------
>
> Waiting on manual testing results, will post updates based on results.
>
>
> Thanks,
>
> Sid Wagle
>
>
Re: Review Request 36287: Installer wizard: cluster deploy failed due
to deadlock
Posted by Jonathan Hurley <jh...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36287/#review90864
-----------------------------------------------------------
Ship it!
Ship It!
- Jonathan Hurley
On July 7, 2015, 8:48 p.m., Sid Wagle wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/36287/
> -----------------------------------------------------------
>
> (Updated July 7, 2015, 8:48 p.m.)
>
>
> Review request for Ambari, Jonathan Hurley, Mahadev Konar, and Myroslav Papirkovskyy.
>
>
> Bugs: AMBARI-12322
> https://issues.apache.org/jira/browse/AMBARI-12322
>
>
> Repository: ambari
>
>
> 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
>
> {code:title=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)
> {code}
>
>
> Diffs
> -----
>
> ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertServiceStateListener.java 44f9b50
>
> Diff: https://reviews.apache.org/r/36287/diff/
>
>
> Testing
> -------
>
> Waiting on manual testing results, will post updates based on results.
>
>
> Thanks,
>
> Sid Wagle
>
>