Skip to content

Conversation

@thompson318
Copy link
Contributor

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.



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.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be worth double checking this. I may have misunderstood how the configuration is done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants