apoorvmittal10 opened a new pull request, #16217:
URL: https://github.com/apache/kafka/pull/16217
The PR moves the blocking call of `describeCluster` to async. Though the
issue coldn't be re-produced in Kafka intgeration tests but a thread block on
`describeCluster` has been observed when using admin describeTopic API in
kafka-rest integrations tests.
The threads blocks indefinetly
```
"kafka-admin-client-thread | adminclient-3" #114 daemon prio=5 os_prio=31
cpu=6.57ms elapsed=417.17s tid=0x00000001364fc200 nid=0x13403 waiting on
condition [0x00000002bb419000]
java.lang.Thread.State: WAITING (parking)
at jdk.internal.misc.Unsafe.park([email protected]/Native Method)
- parking to wait for <0x0000000773804828> (a
java.util.concurrent.CompletableFuture$Signaller)
at
java.util.concurrent.locks.LockSupport.park([email protected]/LockSupport.java:211)
at
java.util.concurrent.CompletableFuture$Signaller.block([email protected]/CompletableFuture.java:1864)
at
java.util.concurrent.ForkJoinPool.unmanagedBlock([email protected]/ForkJoinPool.java:3463)
at
java.util.concurrent.ForkJoinPool.managedBlock([email protected]/ForkJoinPool.java:3434)
at
java.util.concurrent.CompletableFuture.waitingGet([email protected]/CompletableFuture.java:1898)
at
java.util.concurrent.CompletableFuture.get([email protected]/CompletableFuture.java:2072)
at
org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:165)
at
org.apache.kafka.clients.admin.KafkaAdminClient.handleDescribeTopicsByNamesWithDescribeTopicPartitionsApi(KafkaAdminClient.java:2324)
at
org.apache.kafka.clients.admin.KafkaAdminClient.describeTopics(KafkaAdminClient.java:2122)
at org.apache.kafka.clients.admin.Admin.describeTopics(Admin.java:311)
at
io.confluent.kafkarest.controllers.TopicManagerImpl.describeTopics(TopicManagerImpl.java:155)
at
io.confluent.kafkarest.controllers.TopicManagerImpl.lambda$listTopics$2(TopicManagerImpl.java:76)
at
io.confluent.kafkarest.controllers.TopicManagerImpl$$Lambda$1925/0x0000000800891448.apply(Unknown
Source)
at
java.util.concurrent.CompletableFuture$UniCompose.tryFire([email protected]/CompletableFuture.java:1150)
at
java.util.concurrent.CompletableFuture.postComplete([email protected]/CompletableFuture.java:510)
at
java.util.concurrent.CompletableFuture.complete([email protected]/CompletableFuture.java:2147)
at
io.confluent.kafkarest.common.KafkaFutures.lambda$toCompletableFuture$0(KafkaFutures.java:45)
at
io.confluent.kafkarest.common.KafkaFutures$$Lambda$1909/0x0000000800897528.accept(Unknown
Source)
at
org.apache.kafka.common.internals.KafkaFutureImpl.lambda$whenComplete$2(KafkaFutureImpl.java:107)
at
org.apache.kafka.common.internals.KafkaFutureImpl$$Lambda$1910/0x0000000800897750.accept(Unknown
Source)
at
java.util.concurrent.CompletableFuture.uniWhenComplete([email protected]/CompletableFuture.java:863)
at
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire([email protected]/CompletableFuture.java:841)
at
java.util.concurrent.CompletableFuture.postComplete([email protected]/CompletableFuture.java:510)
at
java.util.concurrent.CompletableFuture.complete([email protected]/CompletableFuture.java:2147)
at
org.apache.kafka.common.internals.KafkaCompletableFuture.kafkaComplete(KafkaCompletableFuture.java:39)
at
org.apache.kafka.common.internals.KafkaFutureImpl.complete(KafkaFutureImpl.java:122)
at
org.apache.kafka.clients.admin.KafkaAdminClient$4.handleResponse(KafkaAdminClient.java:2106)
at
org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.handleResponses(KafkaAdminClient.java:1370)
at
org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.processRequests(KafkaAdminClient.java:1523)
at
org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.run(KafkaAdminClient.java:1446)
at java.lang.Thread.run([email protected]/Thread.java:833)
```
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
