[
https://issues.apache.org/jira/browse/KAFKA-21337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TengYao Chi updated KAFKA-21337:
--------------------------------
Description:
configure two bootstrap.servers entries, one using unresolvable.invalid (always
fails DNS resolution) and one pointing at the real broker (always resolves).
Verify the admin client still bootstraps and connects using the resolvable
address.
was:
Inject a custom HostResolver via KafkaAdminClient#createInternal(config,
metrics, hostResolver) that throws UnknownHostException at first, then switch
it to resolve successfully before the configured bootstrap.resolve.timeout.ms
budget expires.
Verify the admin client completes a real call (e.g. listTopics) against the
real broker once resolution succeeds.
IIUC, this could follow the current pattern as ConcurrentListOffsetsRequestTest
> Integration test for async bootstrap resolution recovers after initial DNS
> failure
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-21337
> URL: https://issues.apache.org/jira/browse/KAFKA-21337
> Project: Kafka
> Issue Type: Sub-task
> Components: clients
> Reporter: TengYao Chi
> Assignee: Doyeon Kim
> Priority: Major
>
> configure two bootstrap.servers entries, one using unresolvable.invalid
> (always fails DNS resolution) and one pointing at the real broker (always
> resolves).
> Verify the admin client still bootstraps and connects using the resolvable
> address.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
