Steven Schlansker created KAFKA-21033:
-----------------------------------------
Summary: Regression in backoff algorithm during streams internal
topic create
Key: KAFKA-21033
URL: https://issues.apache.org/jira/browse/KAFKA-21033
Project: Kafka
Issue Type: Bug
Components: streams
Affects Versions: 4.3.1
Environment: Linux amd64
Reporter: Steven Schlansker
KAFKA-10357 refactoring ([#20326|https://github.com/apache/kafka/pull/20326])
extracted the internal-topic creation
loop of InternalTopicManager.makeReady into a createTopics helper and
carried the end-of-round backoff block into the per-topic result loop.
Since 4.3.0, after every successfully created topic, the manager logs
"Topics ... could not be made ready" and sleeps retry.backoff.ms when
other topics of the same batch are not yet iterated. The first
initialization of a topology with N internal topics therefore pays
~(N-1) * retry.backoff.ms of pure sleep even when every create succeeds
immediately: with the 100 ms default, a topology with 168 internal
topics loses ~17 seconds before its first rebalance completes, plus one
spurious INFO line per topic. Before
[#20326|https://github.com/apache/kafka/pull/20326] the backoff ran once per
validation round.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
