search

NHMDenmark / DaSSCo-Integration

This Repo will include integration of dassco storage from northtec
0 stars 0 forks source link

ERDA/ARS time out check for syncing assets #104

Open Baeist opened 2 months ago

Baeist commented 2 months ago

We have seen assets get stuck with the ASSET_RECEIVED status after calling the sync erda endpoint without getting the ERDA _ERROR status. Usually they can simply be synced again and no real harm has happened. Adding a time based check in addition to the normal check that we called the endpoint and received a confirmation is necessary. Setting a time limit we allow an asset to have the ASSET_RECEIVED status and then when that expires we can change our status flag for it back so it will get back into the normal sync flow should solve this. This requires adding an extra sync with erda timestamp to the track db, then implementing the logic for making the checks and changing the flag status back so the asset will be picked back up by the sync erda service.

Baeist commented 1 month ago

Added temporary timestamps and attempts to the track entries. They get checked by the validate sync process and handled according to the their values. This is likely just a reset of the sync process for the asset - but if the problem persists the asset gets an error status. Attempts and time is configurable.