[AMBARI-18652] Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.5.0
• Component/s: ambari-server
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 20/Oct/16 16:58
• Updated: 21/Oct/16 21:26
• Resolved: 21/Oct/16 17:18

Description

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.

Issue Links

• links to: Reviewboard