[
https://issues.apache.org/jira/browse/KAFKA-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huxihx resolved KAFKA-8161.
---------------------------
Resolution: Not A Problem
> Comma conflict when run script bin/kafka-configs.sh with config
> 'follower.replication.throttled.replicas'
> ----------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-8161
> URL: https://issues.apache.org/jira/browse/KAFKA-8161
> Project: Kafka
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.10.2.1
> Reporter: Haiping
> Priority: Minor
>
> when executing config command,it suggest that
> follower.replication.throttled.replicas must match for format
> [partitionId],[brokerId]:[partitionId],[brokerId]:[partitionId],[brokerId]
> etc. but when config like that, it run with the following error:
> bin/kafka-configs.sh --entity-type topics --entity-name topic-test1
> --zookeeper 127.0.0.1:2181/kafka --add-config
> 'follower.replication.throttled.replicas=0,1:1,2' --alter
> Error while executing config command requirement failed: Invalid entity
> config: all configs to be added must be in the format "key=val".
> java.lang.IllegalArgumentException: requirement failed: Invalid entity
> config: all configs to be added must be in the format "key=val".
> at scala.Predef$.require(Predef.scala:224)
> at
> kafka.admin.ConfigCommand$.parseConfigsToBeAdded(ConfigCommand.scala:162)
> at kafka.admin.ConfigCommand$.alterConfig(ConfigCommand.scala:81)
> at kafka.admin.ConfigCommand$.main(ConfigCommand.scala:68)
> at kafka.admin.ConfigCommand.main(ConfigCommand.scala)
> It seem that comma has been the separator of both replicas
> {color:#333333}such as{color} ([partitionId],[brokerId]) and keys such as
> (key=val,key=val).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
