fix: use LogMaxConcurrency for logmq consumer worker#879
Merged
Conversation
The logmq consumer was incorrectly using DeliveryMaxConcurrency instead of LogMaxConcurrency, causing LOG_MAX_CONCURRENCY to be ignored and Pub/Sub to cap unacked messages at the delivery limit. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
alexbouchardd
approved these changes
Apr 24, 2026
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
2 participants
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.
Summary
DeliveryMaxConcurrencyinstead ofLogMaxConcurrencyinbuilder.goLOG_MAX_CONCURRENCYenv var to be entirely ignored, capping Pub/Sub unacked messages at the delivery concurrency limitTest plan
LOG_MAX_CONCURRENCYis respected by the logmq consumer subscription🤖 Generated with Claude Code