[ https://issues.apache.org/jira/browse/KAFKA-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang resolved KAFKA-6928. ---------------------------------- Resolution: Fixed Fix Version/s: 2.1.1 2.2.0 > StreamsPartitionAssignor is double retrying within InternalTopicManager > ----------------------------------------------------------------------- > > Key: KAFKA-6928 > URL: https://issues.apache.org/jira/browse/KAFKA-6928 > Project: Kafka > Issue Type: Improvement > Components: streams > Reporter: Guozhang Wang > Assignee: Guozhang Wang > Priority: Major > Fix For: 2.2.0, 2.1.1 > > > Today inside StreamsPartitionAssingor, we are using the admin client to 1) > check num.partitions for internal topics, 2) try to create internal topics > that are not exist yet. We are using the StreamsConfig.RETRIES_CONFIG inside > the InternalTopicManager to capture thrown exceptions from the resulted > KafkaFuture; however inside the AdminClient, we are again using the same > config with its own retrying logic. > We should get rid of the outer retrying logic later; as of now (2018.05) > there are still some issues with the admin client such that its own retrying > logic is not safe. I'll leave it to [~hachikuji] to decide when admin > client's own retrying is safe to rely on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)