Page History

...

• config.storage.replication.factor – defaults to 3, value must be >= 1
• offset.storage.replication.factor – defaults to 3, value must be >= 1
• status.storage.replication.factor – defaults to 3, value must be >= 1
• offset.storage.partitions – defaults to 25, value must be >= 1
• status.storage.partitions – defaults to 5, value must be >= 1

The topic used for storage of connector configurations must always have exactly one partition, which is why there is no configuration property to set the partition for this topic.

At the time of KIP-154, the AdminClient API required the replication factor and partitions be greater than or equal to one. But more recently, KIP-464 modified the AdminClient APIs to support creating topics by using the broker's default.replication.factor value and/or the broker's num.partitions value. The Kafka Connect distributed worker configuration currently does not support using the broker's default replication factor or number of partitions.

The Kafka Connect distributed worker configuration also does not support defining or passing other topic settings when the Connect worker creates the configuration, offset, and status topics. 

...

The allowed values for the following three five existing Connect distributed worker properties will be changed to also allow -1 to signal that the broker's default replication factor should be used for the newly created topics:

• config.storage.replication.factor
• offset.storage.replication.factor
• status.storage.replication.factor
• offset.storage.partitions
• status.storage.partitions

Also, the distributed worker configuration will be changed to recognize additional optional properties that match the following patterns, and to pass them (without the prefix) to the new topic requests created by the Connect distributed worker when it attempts to create the internal topics:

...