[jira] [Updated] (KAFKA-9300) Create a topic based on the specified brokers
[ https://issues.apache.org/jira/browse/KAFKA-9300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weiwei updated KAFKA-9300: -- Affects Version/s: (was: 2.2.2) 2.3.0 > Create a topic based on the specified brokers > - > > Key: KAFKA-9300 > URL: https://issues.apache.org/jira/browse/KAFKA-9300 > Project: Kafka > Issue Type: New Feature > Components: clients >Affects Versions: 2.3.0 >Reporter: weiwei >Assignee: weiwei >Priority: Major > Fix For: 2.4.0 > > Original Estimate: 120h > Remaining Estimate: 120h > > Generally, A Kafka cluster serves multiple businesses. To reduce the impact > of businesses, many companies isolate brokers to physically isolate > businesses. That is, the topics of certain businesses are created on the > specified brokers. The current topic creation script supports only create > topic according replica-assignment . This function is not convenient for the > service to specify the brokers. Therefore, you need to add this function as > follows: Create a topci based on the specified brokers. The > replica-assignment-brokers parameter is added to indicate the broker range of > the topic distribution. If this parameter is not set, all broker nodes in the > cluster are used. For example, kafka-topics.sh --create --topic test06 > --partitions 2 --replication-factor 1 --zookeeper zkurl -- > --replica-assignment-brokers=1,2. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KAFKA-9300) Create a topic based on the specified brokers
[ https://issues.apache.org/jira/browse/KAFKA-9300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997347#comment-16997347 ] weiwei commented on KAFKA-9300: --- [~huxi_2b] I plan to add a topic-creating config 'replica-assignment-brokers' and the underlying layer still invokes AdminUtils.assignReplicasToBrokers( ). I do not think that the public API modification is involved and maybe KIP is not required. > Create a topic based on the specified brokers > - > > Key: KAFKA-9300 > URL: https://issues.apache.org/jira/browse/KAFKA-9300 > Project: Kafka > Issue Type: New Feature > Components: clients >Affects Versions: 2.2.2 >Reporter: weiwei >Assignee: weiwei >Priority: Major > Fix For: 2.4.0 > > Original Estimate: 120h > Remaining Estimate: 120h > > Generally, A Kafka cluster serves multiple businesses. To reduce the impact > of businesses, many companies isolate brokers to physically isolate > businesses. That is, the topics of certain businesses are created on the > specified brokers. The current topic creation script supports only create > topic according replica-assignment . This function is not convenient for the > service to specify the brokers. Therefore, you need to add this function as > follows: Create a topci based on the specified brokers. The > replica-assignment-brokers parameter is added to indicate the broker range of > the topic distribution. If this parameter is not set, all broker nodes in the > cluster are used. For example, kafka-topics.sh --create --topic test06 > --partitions 2 --replication-factor 1 --zookeeper zkurl -- > --replica-assignment-brokers=1,2. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-9300) Create a topic based on the specified brokers
[ https://issues.apache.org/jira/browse/KAFKA-9300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weiwei updated KAFKA-9300: -- Summary: Create a topic based on the specified brokers (was: Create a topci based on the specified brokers) > Create a topic based on the specified brokers > - > > Key: KAFKA-9300 > URL: https://issues.apache.org/jira/browse/KAFKA-9300 > Project: Kafka > Issue Type: New Feature > Components: clients >Affects Versions: 2.2.2 >Reporter: weiwei >Assignee: weiwei >Priority: Major > Fix For: 2.4.0 > > Original Estimate: 120h > Remaining Estimate: 120h > > Generally, A Kafka cluster serves multiple businesses. To reduce the impact > of businesses, many companies isolate brokers to physically isolate > businesses. That is, the topics of certain businesses are created on the > specified brokers. The current topic creation script supports only create > topic according replica-assignment . This function is not convenient for the > service to specify the brokers. Therefore, you need to add this function as > follows: Create a topci based on the specified brokers. The > replica-assignment-brokers parameter is added to indicate the broker range of > the topic distribution. If this parameter is not set, all broker nodes in the > cluster are used. For example, kafka-topics.sh --create --topic test06 > --partitions 2 --replication-factor 1 --zookeeper zkurl -- > --replica-assignment-brokers=1,2. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KAFKA-9300) Create a topci based on the specified brokers
weiwei created KAFKA-9300: - Summary: Create a topci based on the specified brokers Key: KAFKA-9300 URL: https://issues.apache.org/jira/browse/KAFKA-9300 Project: Kafka Issue Type: New Feature Components: clients Affects Versions: 2.2.2 Reporter: weiwei Assignee: weiwei Fix For: 2.4.0 Generally, A Kafka cluster serves multiple businesses. To reduce the impact of businesses, many companies isolate brokers to physically isolate businesses. That is, the topics of certain businesses are created on the specified brokers. The current topic creation script supports only create topic according replica-assignment . This function is not convenient for the service to specify the brokers. Therefore, you need to add this function as follows: Create a topci based on the specified brokers. The replica-assignment-brokers parameter is added to indicate the broker range of the topic distribution. If this parameter is not set, all broker nodes in the cluster are used. For example, kafka-topics.sh --create --topic test06 --partitions 2 --replication-factor 1 --zookeeper zkurl -- --replica-assignment-brokers=1,2. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KAFKA-1778) Create new re-elect controller admin function
[ https://issues.apache.org/jira/browse/KAFKA-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907088#comment-16907088 ] weiwei commented on KAFKA-1778: --- Is there any progress on this issue? In the preceding solution, a brokerX is specified as the next controler. If the brokerX is faulty and cannot be elected as a controller, the service is risky. A solution is provided. Currently, the controller is available in the broker range. In this way, the controller can be isolated and the controller can be highly reliable. > Create new re-elect controller admin function > - > > Key: KAFKA-1778 > URL: https://issues.apache.org/jira/browse/KAFKA-1778 > Project: Kafka > Issue Type: New Feature >Reporter: Joe Stein >Assignee: Abhishek Nigam >Priority: Major > > kafka --controller --elect -- This message was sent by Atlassian JIRA (v7.6.14#76016)