[
https://issues.apache.org/jira/browse/AMBARI-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595874#comment-15595874
]
Hudson commented on AMBARI-18652:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5844 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5844/])
AMBARI-18652 - Alert Targets Cannot Be Updated Due To Transaction / (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=66259872fede7645be5c49391a3aa8bf13f4c8bf])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertDispatchDAO.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/services/AlertNoticeDispatchServiceTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertGroupEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertTargetEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertNoticeEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java
> Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues
> ------------------------------------------------------------------------
>
> Key: AMBARI-18652
> URL: https://issues.apache.org/jira/browse/AMBARI-18652
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18652.patch
>
>
> There is a JPA timing issue WRT to updating alert targets where lazy loaded
> lists outside of a transaction cause the data set on the {{AlertTargetEnity}}
> to be refreshed from the database.
> While maintaining the bi-directional relationship between
> {{AlertTargetEntity}} and {{AlertGroupEntity}}, and {{IndirectSet}} from JPA
> causes JPA to detect a stale entity from another transaction.
> STR:
> It's more likely to happen when there are active alerts.
> - Create a new alert target for _just_ HDFS
> - Shut down HDFS
> - Try to edit the name of the alert target
> It will return a 200 return code, but the data will not have changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
