root
/
kafka
mirror of https://github.com/apache/kafka.git
1
0
Fork 0
Code Issues Actions 2 Packages Projects Releases Wiki Activity

KAFKA-13917: Avoid calling lookupCoordinator() in tight loop (#12180) 

Reviewers: Luke Chen <showuon@gmail.com>
This commit is contained in:
Viktor Somogyi-Vass 2022-06-10 06:05:05 +02:00 committed by GitHub
parent e67408c859
commit f8f57960c6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
clients/src/main/java/org/apache/kafka/clients/consumer/internals/AbstractCoordinator.java
View File

@ -1438,12 +1438,11 @@ public abstract class AbstractCoordinator implements Closeable {
// clear the future so that after the backoff, if the hb still sees coordinator unknown in // clear the future so that after the backoff, if the hb still sees coordinator unknown in
// the next iteration it will try to re-discover the coordinator in case the main thread cannot // the next iteration it will try to re-discover the coordinator in case the main thread cannot
clearFindCoordinatorFuture(); clearFindCoordinatorFuture();
// backoff properly
AbstractCoordinator.this.wait(rebalanceConfig.retryBackoffMs);
} else { } else {
lookupCoordinator(); lookupCoordinator();
} }
// backoff properly
AbstractCoordinator.this.wait(rebalanceConfig.retryBackoffMs);
} else if (heartbeat.sessionTimeoutExpired(now)) { } else if (heartbeat.sessionTimeoutExpired(now)) {
// the session timeout has expired without seeing a successful heartbeat, so we should // the session timeout has expired without seeing a successful heartbeat, so we should
// probably make sure the coordinator is still healthy. // probably make sure the coordinator is still healthy.