Kafka AdminClient DEFAULT_API_TIMEOUT_MS_CONFIG property not working as expected
Hi, In my java application for kafkaProducer i created Admin and used this to list topics. Admin admin1 = Admin.create(properties). ListTopicsResult listTopicResult = admin1.listTopics(); When producer was not able to connect to broker, thread get stucks at listTopic step. To avoid this i have added DEFAULT_API_TIMEOUT_MS_CONFIG property and have set to 2000ms. so after 2s if producer is not able to connect to broker timeout should happen. properties.put(AdminClientConfig.DEFAULT_API_TIMEOUT_MS_CONFIG,2000). But this does not work as expected. even DEFAULT_API_TIMEOUT_MS_CONFIG with value 2000ms as property timeout didn't happen and thread was struck. Is there any other way to achieve timeout or do we need to configure it in any other way? Also is using AdminClient instead of Admin can have any impact. Thanks in advance Thanks Shruti
[jira] [Created] (KAFKA-14461) StoreQueryIntegrationTest#shouldQuerySpecificActivePartitionStores logic to check for active partitions seems brittle.
Sagar Rao created KAFKA-14461: - Summary: StoreQueryIntegrationTest#shouldQuerySpecificActivePartitionStores logic to check for active partitions seems brittle. Key: KAFKA-14461 URL: https://issues.apache.org/jira/browse/KAFKA-14461 Project: Kafka Issue Type: Bug Reporter: Sagar Rao Assignee: Sagar Rao Newly added test KTableKTableForeignKeyInnerJoinCustomPartitionerIntegrationTest#shouldThrowIllegalArgumentExceptionWhenCustomPartionerReturnsMultiplePartitions as part of KIP-837 passes when run individually but fails when is part of IT class and hence is marked as Ignored. -- This message was sent by Atlassian Jira (v8.20.10#820010)
