I would like to start discussing KIP-1339: Make KafkaConfigBackingStore 
read_write_total_timeout configurable

KIP: 
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1339%3A+Make+KafkaConfigBackingStore+read_write_total_timeout+configurable

In Kafka Connect, the KafkaConfigBackingStore class is responsible for 
persisting connector and task configurations in a Kafka topic. Currently, the 
timeout for synchronous write operations and then reading back from the 
configuration topic is hardcoded via the READ_WRITE_TOTAL_TIMEOUT_MS constant, 
set to 30,000 milliseconds (30 seconds).

While 30 seconds is sufficient for many environments, this hardcoded limit can 
be problematic in some specific scenarios.

There were earlier discussions 
(https://lists.apache.org/thread/flpm1qrm7cwj6fqr1j8c0p8sbqysgv34) on extending 
the timeout value. This KIP proposes making this timeout value a configurable 
parameter.

Any feedback is appreciated.

Thanks and Regards

Henry Cai

Reply via email to