Skip to content
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 cannot consume using older subscriptions if max subscription limi… #9758

Merged
merged 2 commits into from
Mar 1, 2021

Conversation

315157973
Copy link
Contributor

Fixes #9755

Motivation

If maxSubscriptionsPerTopic is set in the broker (or even as a namespace policy), once this limit is reached, broker does not allow consumers to be created for even older subscriptions.

Modifications

Existing subscriptions are not restricted

Verifying this change

TopicPoliciesTest#testMaxSubscriptionsPerTopicWithExistingSubs

@315157973
Copy link
Contributor Author

/pulsarbot run-failure-checks

@zymap zymap merged commit 52a2863 into apache:master Mar 1, 2021
zymap pushed a commit that referenced this pull request Mar 1, 2021
#9758)

Fixes #9755

### Motivation
If maxSubscriptionsPerTopic is set in the broker (or even as a namespace policy), once this limit is reached, broker does not allow consumers to be created for even older subscriptions.

### Modifications
Existing subscriptions are not restricted

### Verifying this change
TopicPoliciesTest#testMaxSubscriptionsPerTopicWithExistingSubs

(cherry picked from commit 52a2863)
@zymap zymap added the cherry-picked/branch-2.7 Archived: 2.7 is end of life label Mar 1, 2021
@315157973 315157973 deleted the max-sub branch March 12, 2021 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-picked/branch-2.7 Archived: 2.7 is end of life release/2.7.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot consume using older subscriptions if max subscription limit is reached
3 participants