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

Avoid to infinitely split bundle #11937

Merged
merged 1 commit into from
Sep 8, 2021
Merged

Avoid to infinitely split bundle #11937

merged 1 commit into from
Sep 8, 2021

Conversation

shoothzj
Copy link
Member

@shoothzj shoothzj commented Sep 7, 2021

Motivation

If there is just one topic, but reached the split conditition. The pulsar broker will went to infinitely splitting bundle.

Modifications

If there is just one topic, we do not split.

Documentation

  • no-need-doc

It's an internal change, no need doc

@codelipenghui codelipenghui added this to the 2.9.0 milestone Sep 7, 2021
@codelipenghui codelipenghui added release/2.8.2 type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages labels Sep 7, 2021
Copy link
Contributor

@eolivelli eolivelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have one question:
Why 1 and not a configurable threshold ? is it for developers / pulsar standalone users ?

@shoothzj
Copy link
Member Author

shoothzj commented Sep 7, 2021

I have one question:
Why 1 and not a configurable threshold ? is it for developers / pulsar standalone users ?

First, It's not a config like minBundleTopics.
Second, it's not only for developer use, let's think a scene

One namespace, one topic/partition, but the topic's rate is high, the bundle split will infinitely splite bundle, make this topic doesn't work.

@shoothzj
Copy link
Member Author

shoothzj commented Sep 7, 2021

I have one question:
Why 1 and not a configurable threshold ? is it for developers / pulsar standalone users ?

And it's meaningless for split bundle that has only one topic

@gaozhangmin
Copy link
Contributor

why bundle contains one topic cannot split? I am confused.

@shoothzj
Copy link
Member Author

shoothzj commented Sep 7, 2021

why bundle contains one topic cannot split? I am confused.

Cause it will lead to infinitely split bundle.

@lhotari
Copy link
Member

lhotari commented Sep 7, 2021

Good catch @shoothzj !

Copy link
Contributor

@eolivelli eolivelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@merlimat merlimat merged commit bef3757 into apache:master Sep 8, 2021
codelipenghui pushed a commit that referenced this pull request Sep 9, 2021
@codelipenghui codelipenghui added the cherry-picked/branch-2.8 Archived: 2.8 is end of life label Sep 9, 2021
lhotari pushed a commit to datastax/pulsar that referenced this pull request Sep 22, 2021
(cherry picked from commit bef3757)
(cherry picked from commit d02653a)
bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-picked/branch-2.8 Archived: 2.8 is end of life release/2.8.2 release/2.9.0 type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants