Details
-
Type: Improvement
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: Daily Data Availability Phase 2
-
Fix Version/s: None
-
Component/s: Event Listener
-
Labels:None
-
Environment:
xml06
Description
If we have an instance of the Event Listener running on more than one server, and the instance that handles the setdatanotstarted event is very backed up (like it was today) but the other instance is handling events just fine, we run into a race condition where DA status may be set to 'in progress' or 'success' and then set to 'not started' once the other server processes the messages.
My suggestion is the code have some logic about not setting it to 'not started' unless there is no entry for that date. This logic could be done elsewhere, like in the Event Listener, but it makes most sense to me to do it here. This will also prevent erroneous reruns.