-
|
From @daria-sorokina-da: "Databases A, B - when does hot-swapping happen? how is it implemented?" |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
When does hot-swapping happen?When the data refresh job completes successfully. The idea is that the newly processed data should not be accessed for search until the job to re-process all donors with the up-to-date nomenclature version has been fully completed. How is it implemented?In the "MatchingAlgorithmPersistent" schema of the shared Atlas database, there is a table containing details of all historic data refresh records. This is not just an audit for support purposes, but provides the definitive source of which database to use:
As part of the data refresh, a row will be added to this table, gradually updated with details on how far through it is, and eventually marked as a success via a boolean column. All in flight searches will finish against the same database they started with (thanks to per-request caching of the "active database" state) - and all new searches will begin against the newly active database. |
Beta Was this translation helpful? Give feedback.
When does hot-swapping happen?
When the data refresh job completes successfully.
The idea is that the newly processed data should not be accessed for search until the job to re-process all donors with the up-to-date nomenclature version has been fully completed.
How is it implemented?
In the "MatchingAlgorithmPersistent" schema of the shared Atlas database, there is a table containing details of all historic data refresh records.
This is not just an audit for support purposes, but provides the definitive source of which database to use:
The database against which the most recent successful data refresh was run should be used for searchAs part of the data refresh, a row will be added to…