See https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=1400542

Update of the JobExecution to assign the JobProfile and the request to process a record come separately. In case Read instance is not synchronising fast enough, some single record operations and importing via API could fail.  See details in https://folio-org.atlassian.net/browse/MODSOURMAN-909#icft=MODSOURMAN-909 and https://folio-org.atlassian.net/browse/MODSOURMAN-906#icft=MODSOURMAN-906. The problem is not relevant for imports initiated via mod-data-import (importing a file) - in this case records come for processing in chunks via Kafka.

Investigate the issue with subsequent requests and define a solution how it can be solved. The goal is to enable the R/W split of the DB for mod-source-record-manager to have some improvements in performance

ORCHID Critical service patch details

1. Describe issue impact on business: By splitting read/write operations, that allows interactions with SRM to be faster.

2. What institutions are affected? (field “Affected Institutions” in Jira to be populated): Any using Data import

3. What is the workaround if exists? None, system is less efficient

4. What areas will be impacted by fix (i.e. what areas need to be retested): Confirm Data import Smoke and Critical path work as expected

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

   • Problem: R/W split of the DB for mod-source-record-manager is disabled to avoid errors on single record operations (https://folio-org.atlassian.net/browse/MODSOURMAN-906#icft=MODSOURMAN-906, https://folio-org.atlassian.net/browse/MODSOURMAN-909#icft=MODSOURMAN-909). Errors occur because request to assign the JobProfile (Update/write of the JobExecution) and the request to process a record (get/read JobExecution) come separately. In case Read instance is not synchronising fast enough, some single record operations and importing via API could fail.

   • Purpose: Enable R/W split of the DB

   • Approach: Change request for getJobExecutionById to go to the main (write) version of the DB

   • Technical risk: Low

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO: After the MODSOURCE and MODSOURMAN patches are applied, we need to retest the Smoke and Critical Path Data Import tests (most of which are automated), and perhaps selected Extended Manual tests. Manual testing across these MODSOURCE and MODSOURMAN changes are likely 3-5 days of work for manual QA, plus some input from PO.

7. What is the roll back plan in case the fix does not work? Revert to previous version, where R/W split was disabled

NOLANA Critical service patch details

1. Describe issue impact on business: By splitting read/write operations, that allows interactions with SRM to be faster.

2. What institutions are affected? (field “Affected Institutions” in Jira to be populated): Any using Data import

3. What is the workaround if exists? None, system is less efficient

4. What areas will be impacted by fix (i.e. what areas need to be retested): Confirm Data import Smoke and Critical path work as expected

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

   • Problem: R/W split of the DB for mod-source-record-manager is disabled to avoid errors on single record operations (https://folio-org.atlassian.net/browse/MODSOURMAN-906#icft=MODSOURMAN-906, https://folio-org.atlassian.net/browse/MODSOURMAN-909#icft=MODSOURMAN-909). Errors occur because request to assign the JobProfile (Update/write of the JobExecution) and the request to process a record (get/read JobExecution) come separately. In case Read instance is not synchronising fast enough, some single record operations and importing via API could fail.

   • Purpose: Enable R/W split of the DB

   • Approach: Change request for getJobExecutionById to go to the main (write) version of the DB

   • Technical risk: Low

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO: After the MODSOURCE and MODSOURMAN patches are applied, we need to retest the Smoke and Critical Path Data Import tests (most of which are automated), and perhaps selected Extended Manual tests. Manual testing across these MODSOURCE and MODSOURMAN changes are likely 3-5 days of work for manual QA, plus some input from PO.

7. What is the roll back plan in case the fix does not work? Revert to previous version, where R/W split was disabled