jira  

Messages by Thread

• • Re: [PR] KAFKA-20116: Make task-offset-sum available to client background thread (1/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Make task-offset-sum available to client background thread (1/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Make task-offset-sum available to client background thread (1/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Make task-offset-sum available to client background thread (1/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Make task-offset-sum available to client background thread (1/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Make task-offset-sum available to client background thread (1/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Make task-offset-sum available to client background thread (1/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Make task-offset-sum available to client background thread (1/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Make task-offset-sum available to client background thread (1/N) [kafka] via GitHub
• [jira] [Updated] (KAFKA-20709) Add built-in SMT for header-based topic routing in Kafka Connect / MirrorMaker 2 with configurable priority across multiple headers kravii (Jira)
• [jira] [Created] (KAFKA-20709) Add built-in SMT for header-based topic routing in Kafka Connect / MirrorMaker 2 with configurable priority across multiple headers kravii (Jira)
• Re: [PR] KAFKA-20199: Use NodeId selector metric tag on controller-only KRaft nodes [kafka] via GitHub
  • Re: [PR] KAFKA-20199: Use NodeId selector metric tag on controller-only KRaft nodes [kafka] via GitHub
• Re: [PR] KAFKA-20237: Re-enqueue InitProducerId request after authentication failure [kafka] via GitHub
  • Re: [PR] KAFKA-20237: Re-enqueue InitProducerId request after authentication failure [kafka] via GitHub
• Re: [PR] KAFKA-20096 Adding rocksdb upgrade and downgrade system test [kafka] via GitHub
  • Re: [PR] KAFKA-20096 Adding rocksdb upgrade and downgrade system test [kafka] via GitHub
• Re: [PR] KAFKA-19878 : Connect | Fixed order of arguments in assertEquals in connect package [kafka] via GitHub
  • Re: [PR] KAFKA-19878 : Connect | Fixed order of arguments in assertEquals in connect package [kafka] via GitHub
• Re: [PR] KAFKA-18874: Fix KRaft controller registration retry on timeout [kafka] via GitHub
  • Re: [PR] KAFKA-18874: Fix KRaft controller registration retry on timeout [kafka] via GitHub
• Re: [PR] KAFKA-19008 Remove scala version from artifacts [kafka] via GitHub
• Re: [PR] KAFKA-19262 Add a test to verify all metrics naming pattern [kafka] via GitHub
• Re: [PR] KAFKA-18477 remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread (1/N) [kafka] via GitHub
• Re: [PR] KAFKA-17798: Add forbidden-apis linting to gradle build [kafka] via GitHub
• Re: [PR] MINOR: Add MockProducer and MockConsumer testing examples [kafka] via GitHub
  • Re: [PR] MINOR: Add MockProducer and MockConsumer testing examples [kafka] via GitHub
• Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
  • Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
  • Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
  • Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
  • Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
  • Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
  • Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
  • Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
  • Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
  • Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
  • Re: [PR] KAFKA-20032: KIP-1265 Automatic detection of internal API usage [kafka] via GitHub
• Re: [PR] MINOR: make processMessages task outputs relocatable for build cache [kafka] via GitHub
• Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
  • Re: [PR] KAFKA-20385 [2/N]: Add setRebalanceListener into *Consumer [kafka] via GitHub
• Re: [PR] WIP: KAFKA-20292: Implement offloaded assignments [kafka] via GitHub
  • Re: [PR] WIP: KAFKA-20292: Implement offloaded assignments [kafka] via GitHub
  • Re: [PR] WIP: KAFKA-20292: Implement offloaded assignments [kafka] via GitHub
  • Re: [PR] WIP: KAFKA-20292: Implement offloaded assignments [kafka] via GitHub
  • Re: [PR] WIP: KAFKA-20292: Implement offloaded assignments [kafka] via GitHub
  • Re: [PR] WIP: KAFKA-20292: Implement offloaded assignments [kafka] via GitHub
  • Re: [PR] WIP: KAFKA-20292: Implement offloaded assignments [kafka] via GitHub
  • Re: [PR] WIP: KAFKA-20292: Implement offloaded assignments [kafka] via GitHub
  • Re: [PR] WIP: KAFKA-20292: Implement offloaded assignments [kafka] via GitHub
• [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Preethi KCS (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Matthias J. Sax (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Preethi KCS (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Matthias J. Sax (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Preethi KCS (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Matthias J. Sax (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Preethi KCS (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Alieh Saeedi (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Preethi KCS (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Alieh Saeedi (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Alieh Saeedi (Jira)
  • [jira] [Commented] (KAFKA-14922) kafka-streams-application-reset deletes topics not belonging to specified application-id Preethi KCS (Jira)
• [PR] KAFKA-15701: Expose the requesting principal to CreateTopicPolicy and AlterConfigPolicy [kafka] via GitHub
  • Re: [PR] KAFKA-15701: Expose the requesting principal to CreateTopicPolicy and AlterConfigPolicy [kafka] via GitHub
  • Re: [PR] KAFKA-15701: Expose the requesting principal to CreateTopicPolicy and AlterConfigPolicy [kafka] via GitHub
• [PR] KAFKA-12759: Rebalance when a static member's subscription changes (classic protocol) [kafka] via GitHub
  • Re: [PR] KAFKA-12759: Rebalance when a static member's subscription changes (classic protocol) [kafka] via GitHub
• Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
  • Re: [PR] KAFKA-19883: [DRAFT] KIP-1289 — Transactional acknowledgments for share groups (state machine + client API + wire schema) [kafka] via GitHub
• Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
• Re: [PR] KAFKA-17397: Ensure ClassicKafkaConsumer sends leave request on close even if interrupted [kafka] via GitHub
  • Re: [PR] KAFKA-17397: Ensure ClassicKafkaConsumer sends leave request on close even if interrupted [kafka] via GitHub
• [jira] [Resolved] (KAFKA-17397) Ensure ClassicKafkaConsumer sends leave request on close even if interrupted Lianet Magrans (Jira)
• [jira] [Resolved] (KAFKA-20522) Refine test coverage for consumer close-on-interrupt best-effort behavior Lianet Magrans (Jira)
• [jira] [Created] (KAFKA-20708) KIP-1358: Gradual and gated preferred-leader election in the KRaft controller Haifeng Chen (Jira)
• [jira] [Updated] (KAFKA-20681) Consolidate heartbeat success path for consumer and shareConsumer Lianet Magrans (Jira)
• [jira] [Resolved] (KAFKA-20674) Speed up ShareConsumerTest.testAcquisitionLockTimeoutOnConsumer Jheng-Sing Chen (Jira)
• [PR] KAFKA-20693: Fix NPE in AbstractHerder config-validation error handling [kafka] via GitHub
  • Re: [PR] KAFKA-20693: Fix NPE in AbstractHerder config-validation error handling [kafka] via GitHub
  • Re: [PR] KAFKA-20693: Fix NPE in AbstractHerder config-validation error handling [kafka] via GitHub
  • Re: [PR] KAFKA-20693: Fix NPE in AbstractHerder config-validation error handling [kafka] via GitHub
• Re: [PR] KAFKA-20490: Add transaction buffer framework [kafka] via GitHub
  • Re: [PR] KAFKA-20490: Add transaction buffer framework [kafka] via GitHub
  • Re: [PR] KAFKA-20490: Add transaction buffer framework [kafka] via GitHub
• Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
  • Re: [PR] MINOR; Refactor KRaft API around message handling [kafka] via GitHub
• [PR] MINOR: Migrate AuthorizerIntegrationTest to ClusterInstance [kafka] via GitHub
  • Re: [PR] KAFKA-19042 Move AuthorizerIntegrationTest to client-integration-tests module [kafka] via GitHub
  • Re: [PR] KAFKA-19042 Move AuthorizerIntegrationTest to client-integration-tests module [kafka] via GitHub
  • Re: [PR] MINOR: Migrate AuthorizerIntegrationTest to ClusterInstance [kafka] via GitHub
  • Re: [PR] MINOR: Migrate AuthorizerIntegrationTest to ClusterInstance [kafka] via GitHub
  • Re: [PR] MINOR: Migrate AuthorizerIntegrationTest to ClusterInstance [kafka] via GitHub
  • Re: [PR] MINOR: Migrate AuthorizerIntegrationTest to ClusterInstance [kafka] via GitHub
  • Re: [PR] MINOR: Rewrite AuthorizerIntegrationTest and rename to ConsumerGroupCommandAuthorizationTest [kafka] via GitHub
  • Re: [PR] MINOR: Rewrite AuthorizerIntegrationTest and rename to ConsumerGroupCommandAuthorizationTest [kafka] via GitHub
  • Re: [PR] MINOR: Rewrite AuthorizerIntegrationTest and rename to ConsumerGroupCommandAuthorizationTest [kafka] via GitHub
  • Re: [PR] MINOR: Rewrite AuthorizerIntegrationTest and rename to ConsumerGroupCommandAuthorizationTest [kafka] via GitHub
• Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub

• Earlier messages
• Later messages