This repository has been archived by the owner on Sep 1, 2022. It is now read-only.
Fix collection update during the catalog reinitialization #232
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re-initialize the catalog through the "Reinitialize" option (/thredds/admin/debug?catalogs/reinit) doesn't manage correctly the job and trigger scheduler, because the job and triggers are already sheduled. Example of warn and error displayed in the fc.collection.log files:
In order to fix this issue a new method has been implemented to reinitialize the scheduler when the DataRootHandler.reinit() is called. We haven't modified the TDM because we don't use it, and it is likely that some modification are needed.
Best regards,
Kristian