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.
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.