You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2016/10/20 17:03:59 UTC
[jira] [Updated] (AMBARI-18652) Alert Targets Cannot Be Updated Due
To Transaction / Cache Timing Issues
[ https://issues.apache.org/jira/browse/AMBARI-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley updated AMBARI-18652:
-------------------------------------
Attachment: AMBARI-18652.patch
> 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)