Status: Closed (View Workflow)
ACQ Sprint 134, ACQ Sprint 135, ACQ Sprint 136, ACQ Sprint 166
Poppy (R2 2023)
Implementation coding issue
When EDIFACT orders export job is scheduled to run every one hour(no matter which type of scheduling is used) if it is deployed in multi nodes(multi instances of mod-data-export-spring), the scheduler triggers on both the nodes. This is expected as each node is a separate service altogether.
Open question : Is deploying multiple mod-data-export-spring instances per tenant a default setting?
If only one instance is deployed, then there is no problem. But if many instances, then issue must be fixed.
Also make sense to include information about unexpected behavior of scheduling in case more then one instances deployed.
Steps to Reproduce:
- Prepare EDIFACT scheduled configuration
- Deploy 2 instances of the mod-data-export-spring for tenant
At triggered time the export Job is ran only once and orders exported once.
At triggered time the export Job is ran twice and orders exported twice.
Looks like can be fixed as proposed : https://dzone.com/articles/implementing-scheduler-lock
Implementation : https://github.com/lukas-krecan/ShedLock
1. Add dependencies
2. Create ShedLock table
- is defined by
UXPROD-3944 Thunderjet - Poppy - RCA I&A
- In progress
- relates to
MODEXPS-185 Prepare initial setup for introducing Quartz as a scheduler in mod-data-export-spring
- mentioned in