Spike: Define an approach how to store scheduling configuration In DB
Description
Environment
None
Potential Workaround
None
clones
defines
Checklist
hideTestRail: Results
Activity
Show:
Serhii_Nosko December 26, 2022 at 5:11 PM
Implementation story based on spike results has been created where described all necessary information: https://folio-org.atlassian.net/browse/MODEXPS-185
Closing this spike as Done
Done
Details
Details
Assignee
Dzmitry Butramyou
Dzmitry ButramyouReporter
Serhii_Nosko
Serhii_NoskoPriority
P3Story Points
2
Sprint
None
Development Team
Thunderjet
Release
Orchid (R1 2023)
Affected Institution
!!!ALL!!!
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created December 12, 2022 at 1:56 PM
Updated December 26, 2022 at 5:11 PM
Resolved December 26, 2022 at 5:11 PM
TestRail: Cases
TestRail: Runs
All out jobs scheduling configuration strored in memory now, need to define appraoch how we can move it to DB.
It can resolve issues that now it is impossible to deploy multiple instances of mod-data-export-worker module, modules can fetch this configs from DB after restart and we will improve observability of our jobs scheduling statuses