-
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
Add limit of max partitions per partitioned topic #6793
Labels
type/feature
The PR added a new feature or issue requested a new feature
Milestone
Comments
equanz
added
the
type/feature
The PR added a new feature or issue requested a new feature
label
Apr 22, 2020
1 task
sijie
pushed a commit
that referenced
this issue
Apr 29, 2020
#6794) Fixes #6793 ### Motivation Now broker, can't set max number of partitions per partitioned topic. So we can't prevent to create partitioned topic by many partitions from server side. In this PR, introduce limit of max partitions to broker and to be able to control it. ### Modifications Add `maxNumPartitionsPerPartitionedTopic` config to broker and compare with numPartitions at create or update partitioned topic. If the config is set to `0`(is default), then disable the check.
gaoran10
pushed a commit
to gaoran10/pulsar
that referenced
this issue
May 5, 2020
apache#6794) Fixes apache#6793 ### Motivation Now broker, can't set max number of partitions per partitioned topic. So we can't prevent to create partitioned topic by many partitions from server side. In this PR, introduce limit of max partitions to broker and to be able to control it. ### Modifications Add `maxNumPartitionsPerPartitionedTopic` config to broker and compare with numPartitions at create or update partitioned topic. If the config is set to `0`(is default), then disable the check.
gaoran10
pushed a commit
to gaoran10/pulsar
that referenced
this issue
May 5, 2020
apache#6794) Fixes apache#6793 ### Motivation Now broker, can't set max number of partitions per partitioned topic. So we can't prevent to create partitioned topic by many partitions from server side. In this PR, introduce limit of max partitions to broker and to be able to control it. ### Modifications Add `maxNumPartitionsPerPartitionedTopic` config to broker and compare with numPartitions at create or update partitioned topic. If the config is set to `0`(is default), then disable the check.
Huanli-Meng
pushed a commit
to Huanli-Meng/pulsar
that referenced
this issue
May 27, 2020
apache#6794) Fixes apache#6793 ### Motivation Now broker, can't set max number of partitions per partitioned topic. So we can't prevent to create partitioned topic by many partitions from server side. In this PR, introduce limit of max partitions to broker and to be able to control it. ### Modifications Add `maxNumPartitionsPerPartitionedTopic` config to broker and compare with numPartitions at create or update partitioned topic. If the config is set to `0`(is default), then disable the check.
huangdx0726
pushed a commit
to huangdx0726/pulsar
that referenced
this issue
Aug 24, 2020
apache#6794) Fixes apache#6793 ### Motivation Now broker, can't set max number of partitions per partitioned topic. So we can't prevent to create partitioned topic by many partitions from server side. In this PR, introduce limit of max partitions to broker and to be able to control it. ### Modifications Add `maxNumPartitionsPerPartitionedTopic` config to broker and compare with numPartitions at create or update partitioned topic. If the config is set to `0`(is default), then disable the check.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now broker, can't set max number of partitions per partitioned topic. So we can't prevent to create partitioned topic by many partitions from server side.
The text was updated successfully, but these errors were encountered: