[
https://issues.apache.org/jira/browse/AMBARI-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595720#comment-15595720
]
Hadoop QA commented on AMBARI-18652:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834436/AMBARI-18652.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.agent.TestHeartbeatHandler
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8968//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8968//console
This message is automatically generated.
> 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)
