[ingest] Check for keyhash on startup #1189
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nanjiangshu
reviewed
Dec 12, 2024
nanjiangshu
reviewed
Dec 12, 2024
nanjiangshu
reviewed
Dec 12, 2024
nanjiangshu
reviewed
Dec 12, 2024
nanjiangshu
reviewed
Dec 12, 2024
Check that a keyhash exists in the database before start processing any messages. A timer counts down for 5 minutes and if no keyhash exists by then an error will be logged and ingest will restart.
jbygdell
force-pushed
the
feature/ingest-check-for-hash
branch
from
77f9b05 to
73f8a7c
Compare
|
Rebased so needs to be reapproved. |
nanjiangshu
approved these changes
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related issue(s) and PR(s)
This PR closes #1164 .
Description
Check that a keyhash exists in the database before start processing any messages. A timer counts down for 5 minutes and if no keyhash exists by then an error will be logged and ingest will restart.
No messages will be processed before this check completes.
How to test
make build-all
make sda-s3-up
docker logs -f ingest
"no crypt4gh key hash registered" will be printed every 30 seconds and after 5 minutes the container will restart.
If
make integrationtest-sdais used ingest will Print the same message a few times until the tests reaches11_api_test. Then it will process the messages as normal for the ingestion test.