Attila Sasvari created OOZIE-3134:
-------------------------------------
Summary: Potential inconsistency between the in-memory SLA map and
the Oozie database
Key: OOZIE-3134
URL: https://issues.apache.org/jira/browse/OOZIE-3134
Project: Oozie
Issue Type: Bug
Reporter: Attila Sasvari
Upon {{SLACalculatorMemory.addRegistration}}, Oozie puts an entry into an
in-memory concurrent hashmap ("slaMap"), and later [persists
it|https://github.com/apache/oozie/blob/50f4b5984832941f1341586e43fd832c293b3275/core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java#L380]
in the Oozie database.
However, if there is a failure during the database operation, a
{{JPAExecutorException}} is thrown, and the entry [is not removed from the SLA
map|
https://github.com/apache/oozie/blob/50f4b5984832941f1341586e43fd832c293b3275/core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java#L393].
It may introduce inconsistency between the Oozie database and the SLA map.
To prevent this, a rollback mechanism (with proper logging) should be
implemented. It would also make sense to do more sanity/consistency check in
the Oozie server.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
