Open
Conversation
thompson318
commented
Jul 22, 2025
|
|
||
|
|
||
| EMAP is run as a collection of docker containers, each providing a single service such as RabbitMQ. We take the latest RabbitMQ management image from dockerhub and configure it as required. This involves setting ports, authentication and details such as maximum queue size and waiting times. As the RabbitMQ component sits in the middle of the pipeline it is necessary to spin up a version of RabbitMQ even if only testing part of the full pipeline. We configure to 1M hl7 messages and 100K hoover messages to be queued at any point to avoid loss of disk space when a large amount of messages are being processed. In general this is only likely to apply when we are starting off a run from scratch. The normal day to day running of EMAP should not encounter memory problems. | ||
| EMAP is run as a collection of docker containers, each providing a single service such as RabbitMQ. We take the latest RabbitMQ management image from dockerhub and configure it as required. This involves setting ports, authentication and details such as maximum queue size and waiting times. As the RabbitMQ component sits in the middle of the pipeline it is necessary to spin up a version of RabbitMQ even if only testing part of the full pipeline. We configure to [100k hl7 messages](https://github.com/SAFEHR-data/emap/blob/f2edcbc0aa8a9c0c87b1f01892ba69e67b9ec228/hl7-reader/src/main/resources/application.properties#L28) and [1M hoover messages](https://github.com/SAFEHR-data/hoover/blob/3f0e196f71dd57f09a810e61fa6e1c637cd9b423/src/main/resources/application.properties#L19) to be queued at any point to avoid loss of disk space when a large amount of messages are being processed. In general this is only likely to apply when we are starting off a run from scratch. The normal day to day running of EMAP should not encounter memory problems. |
Contributor
Author
There was a problem hiding this comment.
Would be worth double checking this. I may have misunderstood how the configuration is done.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR fixes some broken links I picked up during onboarding (which otherwise seemed to go OK). I also changed a line about the RabbitMQ size for Hoover vs. HL7. What's in the documentation looks different to what's in the configuration files to me.
Documentation: Hoover = 100K ; HL7 = 1M
Configuration: Hoover = 1M ; HL7 = 100K.