-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[improve] [broker] [break change] Do not create partitioned DLQ/Retry topic automatically #22705
Merged
Conversation
This file contains 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
poorbarcode
requested review from
lhotari,
Technoboy-,
eolivelli and
codelipenghui
May 13, 2024 18:51
pulsar-broker/src/main/java/org/apache/pulsar/broker/service/BrokerService.java
Show resolved
Hide resolved
poorbarcode
changed the title
[improve] [broker] Do not create partitioned DLQ/Retry topic automatically
[improve] [broker] [break change] Do not create partitioned DLQ/Retry topic automatically
May 14, 2024
cc @shibd, I remember we discussed this place. |
Technoboy-
approved these changes
May 14, 2024
/pulsarbot rerun-failure-checks |
dao-jun
previously approved these changes
May 14, 2024
I sent a comment to the mail list, PTAL https://lists.apache.org/thread/x5x5kyxwypothwsmrb7x3fflhklrdzb9 |
dao-jun
approved these changes
May 15, 2024
dao-jun
added
the
release/important-notice
The changes which are important should be mentioned in the release note
label
May 15, 2024
shibd
approved these changes
May 15, 2024
nikhil-ctds
pushed a commit
to datastax/pulsar
that referenced
this pull request
May 31, 2024
… topic automatically (apache#22705) (cherry picked from commit f07b3a0) (cherry picked from commit 6ec15d8)
nikhil-ctds
pushed a commit
to datastax/pulsar
that referenced
this pull request
Jun 4, 2024
… topic automatically (apache#22705) (cherry picked from commit f07b3a0) (cherry picked from commit 6ec15d8)
mukesh154
pushed a commit
to cognitree/ds_pulsar
that referenced
this pull request
Jun 4, 2024
… topic automatically (apache#22705) (cherry picked from commit f07b3a0) (cherry picked from commit 6ec15d8)
srinath-ctds
pushed a commit
to datastax/pulsar
that referenced
this pull request
Jun 7, 2024
… topic automatically (apache#22705) (cherry picked from commit f07b3a0) (cherry picked from commit 6ec15d8)
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
cherry-picked/branch-3.0
doc-not-needed
Your PR changes do not impact docs
ready-to-test
release/important-notice
The changes which are important should be mentioned in the release note
release/3.0.6
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.
Discussion: https://lists.apache.org/thread/t756oy8881vqf9fz2zzgk3y04zsyykbh
Motivation
After you set
defaultNumPartitions
to16
, you will get16
partitions per topic, and16*16
DLQ partitions per subscription, you will get a huge number of DLQs if you have more than one subscription under one topic. For example:t1
with16
partitionst1-partition-0
,t1-partition-1
...tp-partition-15
.16*16
DLQs per subscriptiont1-partition-0-{subscription}-DLQ-partition-0
t1-partition-0-{subscription}-DLQ-partition-1
t1-partition-15-{subscription}-DLQ-partition-15
t1-partition-1-{subscription}-DLQ-partition-0
t1-partition-1-{subscription}-DLQ-partition-1
t1-partition-15-{subscription}-partition-15
Issue both partitioned DLQ and non-partitioned DLQ were created automatically.
{allowAutoTopicCreation=true, defaultNumPartitions=1, allowAutoTopicCreationType=partitioned}
< 3.1
partitions: 1
.3.1
, the client mistakenly assumed{tenant}/{namespace}/{topic}-partition-0-{subscription}-DLQ-partition-0
is{tenant}/{namespace}/{topic}-partition-0-{subscription}-DLQ
due to the bug that was fixed by [fix] [broker] Fix wrong logic of method TopicName.getPartition(int index) #19841.{tenant}/{namespace}/{topic}-partition-0-{subscription}-DLQ
Eventually, you will get both partitioned and non-partitioned DLQ.
Modifications
Documentation
doc
doc-required
doc-not-needed
doc-complete
Matching PR in forked repository
PR in forked repository: x