Clone of Poppy issue: MODSOURCE-689

Add flag in DB to indicate that background job to clean up OLD records is executed. In case there are multiple instances of mod-srs modules, this will prevent other instance from triggering the job when it is already in progress.

ORCHID Critical service patch details

1. Describe issue impact on business The changes prevent the SRS module instances from blocking each other while attempting to delete marc indexers for the same tenant and subsequently reduce the load on the database.

2. What institutions are affected? (field “Affected Institutions” in Jira to be populated) - All institutions that upgraded/upgrading to Orchid CSP 5 and whose environments contain more than one instance of the SRS module.

3. What is the workaround if exists? None.

4. What areas will be impacted by fix (i.e. what areas need to be retested) Data Import Smoke and CP automated tests

5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high). 

   • Purpose: to prevent the SRS module instances from blocking each other while trying to delete marc indexers on the same tenant

   • Technical explanation:

     • a lock mechanism was applied for deleting marc indexers on a tenant to prevent this deletion from being executed by multiple module instances for the same tenant simultaneously.  If the module instance sees that the lock is already obtained, it will move on to the next tenant.

   • Level of effort: Work is complete and level effort was medium.

   • Technical risk: Minimal risk.

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO. Test automated Data Import Smoke and Critical Path. Level of effort: 2 hours

7. What is the roll back plan in case the fix does not work? Revert to previous version