fix: Issue with RabbitMQ Message Consumption #134
+32
−26
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.
Fix Issue with RabbitMQ Message Consumption
This update addresses two key issues related to message consumption from RabbitMQ:
Goroutine Management for Output Channel:
Currently, when a message is received from RabbitMQ, it is passed to the output channel using a goroutine. This results in a new goroutine being created for every message. Once the output channel reaches its buffer limit, all the goroutines are blocked, waiting for space in the channel to send the messages. This update optimizes the message handling to prevent unnecessary goroutine buildup.
Set Prefetch Count to Match Output Channel Buffer:
RabbitMQ, by default, fetches all messages at once unless a prefetch count is specified. To avoid overwhelming the system with too many messages at once, we have set the RabbitMQ prefetch count to match the buffer size of the output channel. This ensures that only a manageable number of messages are fetched and processed at a time.