-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix[MQB]: remove maxDeliveryAttempts range check #496
Fix[MQB]: remove maxDeliveryAttempts range check #496
Conversation
687408a
to
31dc7b8
Compare
fdaf867
to
186ba23
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good test and change. I think we should try to squash some of these changes for the sake of the commit history, and maybe rip one change out into its own commit.
654d77b
to
ee0c1ea
Compare
- The change made in _crash_consumer_restart_leader comment is to match the comment with the code. - Before removing the if block in `mqbblp_domain.cpp`, `maxDeliveryAttempts` is reset to 5 if it's between 1-4, which is wrong since we want users to be able to set it to any value. The test `test_poison_rda_reset_priority_active` originally set `maxDeliveryAttempts` to 2 but attempted 3 deliveries. Before removing the if block this would work since `maxDeliveryAttempts` is reset to 5, but after the fix, the initial value for `maxDeliveryAttempts` should also change to 3. Signed-off-by: Emelia Lei <wlei29@bloomberg.net>
ee0c1ea
to
f7ea92b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, I'll wait for CI to fire one more time before merging, but LGTM
Test failure seems unrelated; will look into in a different changeset. |
A user uncovered an unfortunate (and undocumented) limitation in the behavior of poison pill configurations, we do not allow users to set this to 1-4 (using the default broker configurations).
We should allow users to configure these as valid values for the number of delivery attempts.