jira  

Messages by Thread

• • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
  • Re: [PR] MINOR: Move partitions == 0 logic from waitForTopic to waitTopicDeletion [kafka] via GitHub
• [jira] [Commented] (KAFKA-19430) Don't fail on RecordCorruptedException Uladzislau Blok (Jira)
  • [jira] [Commented] (KAFKA-19430) Don't fail on RecordCorruptedException Matthias J. Sax (Jira)
• [jira] [Assigned] (KAFKA-19430) Don't fail on RecordCorruptedException Uladzislau Blok (Jira)
• Re: [PR] KAFKA-19299: Fix race condition in RemoteIndexCacheTest [kafka] via GitHub
  • Re: [PR] KAFKA-19299: Fix race condition in RemoteIndexCacheTest [kafka] via GitHub
• [PR] MINOR: Use <code> block instead of backtick [kafka] via GitHub
  • Re: [PR] MINOR: Use <code> block instead of backtick [kafka] via GitHub
  • Re: [PR] MINOR: Use <code> block instead of backtick [kafka] via GitHub
  • Re: [PR] MINOR: Use <code> block instead of backtick [kafka] via GitHub
  • Re: [PR] MINOR: Use <code> block instead of backtick [kafka] via GitHub
  • Re: [PR] MINOR: Use <code> block instead of backtick [kafka] via GitHub
• Re: [PR] KAFKA 18238 - fIdentify the first commit where a test became flaky [kafka] via GitHub
  • Re: [PR] KAFKA 18238 - fIdentify the first commit where a test became flaky [kafka] via GitHub
• Re: [PR] Bug fixes for delete and state epoch. [kafka] via GitHub
  • Re: [PR] Bug fixes for delete and state epoch. [kafka] via GitHub
• Re: [PR] KAFKA-19443: test-common ClusterInstance should make it easy to have more listeners [kafka] via GitHub
• [jira] [Updated] (KAFKA-18035) TransactionsTest testBumpTransactionalEpochWithTV2Disabled failed on trunk Chia-Ping Tsai (Jira)
• [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
• Re: [PR] MINOR: Cleanups in ConfigurationUtils [kafka] via GitHub
  • Re: [PR] MINOR: Cleanups in ConfigurationUtils [kafka] via GitHub
• [PR] KAFKA-19474: Move WARN log on log truncation below HWM [kafka] via GitHub
  • Re: [PR] KAFKA-19474: Move WARN log on log truncation below HWM [kafka] via GitHub
  • Re: [PR] KAFKA-19474: Move WARN log on log truncation below HWM [kafka] via GitHub
  • Re: [PR] KAFKA-19474: Move WARN log on log truncation below HWM [kafka] via GitHub
  • Re: [PR] KAFKA-19474: Move WARN log on log truncation below HWM [kafka] via GitHub
  • Re: [PR] KAFKA-19474: Move WARN log on log truncation below HWM [kafka] via GitHub
  • Re: [PR] KAFKA-19474: Move WARN log on log truncation below HWM [kafka] via GitHub
• [jira] [Updated] (KAFKA-19474) Wrong placement of WARN log for truncation below HWM Gaurav Narula (Jira)
  • [jira] [Updated] (KAFKA-19474) Wrong placement of WARN log for truncation below HWM Gaurav Narula (Jira)
  • [jira] [Updated] (KAFKA-19474) Wrong placement of WARN log for truncation below HWM Gaurav Narula (Jira)
• [jira] [Created] (KAFKA-19474) Wrong placement of WARN log for truncation below HWM Gaurav Narula (Jira)
• [jira] [Assigned] (KAFKA-19474) Wrong placement of WARN log for truncation below HWM Gaurav Narula (Jira)
• [jira] [Created] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes dyingjiecai (Jira)
• [jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2 dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2 dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2 dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2 dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2 dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2 dyingjiecai (Jira)
  • [jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2 dyingjiecai (Jira)
• [jira] [Created] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2 dyingjiecai (Jira)
• [jira] [Commented] (KAFKA-19471) Enable acknowledgement for a record which could not be deserialized Lan Ding (Jira)
  • [jira] [Commented] (KAFKA-19471) Enable acknowledgement for a record which could not be deserialized Andrew Schofield (Jira)
  • [jira] [Commented] (KAFKA-19471) Enable acknowledgement for a record which could not be deserialized Lan Ding (Jira)
• [jira] [Created] (KAFKA-19471) Enable acknowledgement for a record which could not be deserialized Andrew Schofield (Jira)
• [jira] [Resolved] (KAFKA-19468) Share group epoch increments on every heartbeat if subscribed topics removed Andrew Schofield (Jira)
• [PR] KAFKA-19470 Avoid creating loggers repeatedly to affect the performance of request processing [kafka] via GitHub
  • Re: [PR] KAFKA-19470 Avoid creating loggers repeatedly to affect the performance of request processing [kafka] via GitHub
  • Re: [PR] KAFKA-19470 Avoid creating loggers repeatedly to affect the performance of request processing [kafka] via GitHub
  • Re: [PR] KAFKA-19470 Avoid creating loggers repeatedly to affect the performance of request processing [kafka] via GitHub
  • Re: [PR] KAFKA-19470 Avoid creating loggers repeatedly to affect the performance of request processing [kafka] via GitHub
• [jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing terrytlu (Jira)
  • [jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing terrytlu (Jira)
  • [jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing terrytlu (Jira)
  • [jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing terrytlu (Jira)
  • [jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing terrytlu (Jira)
  • [jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing terrytlu (Jira)
  • [jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing terrytlu (Jira)
  • [jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing terrytlu (Jira)
• [jira] [Created] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing terrytlu (Jira)
• [jira] [Resolved] (KAFKA-19363) Enhance share group assignor for heterogeneous subscription type Andrew Schofield (Jira)
• [jira] [Resolved] (KAFKA-19362) Enhance share group assignor for homogeneous subscription type Andrew Schofield (Jira)
• [PR] KAFKA-19457: Make share group init retry interval configurable. [kafka] via GitHub
  • Re: [PR] KAFKA-19457: Make share group init retry interval configurable. [kafka] via GitHub
  • Re: [PR] KAFKA-19457: Make share group init retry interval configurable. [kafka] via GitHub
  • Re: [PR] KAFKA-19457: Make share group init retry interval configurable. [kafka] via GitHub
  • Re: [PR] KAFKA-19457: Make share group init retry interval configurable. [kafka] via GitHub
  • Re: [PR] KAFKA-19457: Make share group init retry interval configurable. [kafka] via GitHub
  • Re: [PR] KAFKA-19457: Make share group init retry interval configurable. [kafka] via GitHub
  • Re: [PR] KAFKA-19457: Make share group init retry interval configurable. [kafka] via GitHub
  • Re: [PR] KAFKA-19457: Make share group init retry interval configurable. [kafka] via GitHub
• Re: [PR] KAFKA-19048: Minimal movement replica balancing algorithm for reassignment [kafka] via GitHub
  • Re: [PR] KAFKA-19048: Minimal movement replica balancing algorithm for reassignment [kafka] via GitHub
• [jira] [Resolved] (KAFKA-19456) State and leader epoch should only be used for validation and not be updated in share coordinator write state RPC. Sushant Mahajan (Jira)
• [jira] [Resolved] (KAFKA-19455) Make unknown_topic_or_partition error retriable by the persister state manager. Sushant Mahajan (Jira)
• [jira] [Resolved] (KAFKA-19454) Share group delete should be resilient to metadata image issues in group coordinator. Sushant Mahajan (Jira)
• [jira] [Commented] (KAFKA-19444) SASL GSSAPI not working with librdkafka and AK 4.x Emanuele Sabellico (Jira)
  • [jira] [Commented] (KAFKA-19444) SASL GSSAPI not working with librdkafka and AK 4.x Ismael Juma (Jira)
  • [jira] [Commented] (KAFKA-19444) SASL GSSAPI not working with librdkafka and AK 4.x Ismael Juma (Jira)
  • [jira] [Commented] (KAFKA-19444) SASL GSSAPI not working with librdkafka and AK 4.x Ismael Juma (Jira)
• [jira] [Commented] (KAFKA-19469) Share group supports dead letter queue Lan Ding (Jira)
  • [jira] [Commented] (KAFKA-19469) Share group supports Dead Letter queue Andrew Schofield (Jira)
  • [jira] [Commented] (KAFKA-19469) Share group supports Dead Letter queue Lan Ding (Jira)
  • [jira] [Commented] (KAFKA-19469) Share group supports Dead Letter queue Andrew Schofield (Jira)
  • [jira] [Commented] (KAFKA-19469) Share group supports Dead Letter queue Lan Ding (Jira)
• [jira] [Updated] (KAFKA-19469) Share group supports dead letter queue Lan Ding (Jira)
  • [jira] [Updated] (KAFKA-19469) Share group supports Dead Letter queue Lan Ding (Jira)
• [jira] [Created] (KAFKA-19469) Share group supports dead letter queue Lan Ding (Jira)
• Re: [PR] KAFKA-18854:Move DynamicConfig to server module [kafka] via GitHub
  • Re: [PR] KAFKA-18854:Move DynamicConfig to server module [kafka] via GitHub
• Re: [PR] Use switch expressions introduced in Java 14 to simplify code [kafka] via GitHub
• [PR] KAFKA-19461: Add share group admin integration tests to PlaintextAdminIntegrationTest [kafka] via GitHub
  • Re: [PR] KAFKA-19461: Add share group admin integration tests to PlaintextAdminIntegrationTest [kafka] via GitHub
  • Re: [PR] KAFKA-19461: Add share group admin integration tests to PlaintextAdminIntegrationTest [kafka] via GitHub
  • Re: [PR] KAFKA-19461: Add share group admin integration tests to PlaintextAdminIntegrationTest [kafka] via GitHub
  • Re: [PR] KAFKA-19461: Add share group admin integration tests to PlaintextAdminIntegrationTest [kafka] via GitHub
  • Re: [PR] KAFKA-19461: Add share group admin integration tests to PlaintextAdminIntegrationTest [kafka] via GitHub
• [PR] KAFKA-18035: Backport TransactionsTest testBumpTransactionalEpochWithTV2Disabled failed on trunk [kafka] via GitHub
  • Re: [PR] KAFKA-18035: Backport TransactionsTest testBumpTransactionalEpochWithTV2Disabled failed on trunk [kafka] via GitHub
• [PR] KAFKA-19468: Ignore unsubscribed topics when computing share assignment [kafka] via GitHub
  • Re: [PR] KAFKA-19468: Ignore unsubscribed topics when computing share assignment [kafka] via GitHub
  • Re: [PR] KAFKA-19468: Ignore unsubscribed topics when computing share assignment [kafka] via GitHub
  • Re: [PR] KAFKA-19468: Ignore unsubscribed topics when computing share assignment [kafka] via GitHub
  • Re: [PR] KAFKA-19468: Ignore unsubscribed topics when computing share assignment [kafka] via GitHub
• [jira] [Created] (KAFKA-19468) Share group epoch increments on every heartbeat if subscribed topics removed Andrew Schofield (Jira)
• [jira] [Updated] (KAFKA-19453) Handle Share group records replay in group coordinator for non-existent share groups. Sushant Mahajan (Jira)
  • [jira] [Updated] (KAFKA-19453) Handle Share group records replay in group coordinator for non-existent share groups. Sushant Mahajan (Jira)
• [jira] [Updated] (KAFKA-19453) Handle Share group records replay in group coordinator for non-existent groups. Sushant Mahajan (Jira)
• [jira] [Updated] (KAFKA-19453) Handle ShareGroupStatePartitionMetadata replay in group coordinator for non-existent groups. Apoorv Mittal (Jira)
  • [jira] [Updated] (KAFKA-19453) Handle ShareGroupStatePartitionMetadata replay in group coordinator for non-existent groups. Apoorv Mittal (Jira)
  • [jira] [Updated] (KAFKA-19453) Handle ShareGroupStatePartitionMetadata replay in group coordinator for non-existent groups. Apoorv Mittal (Jira)
  • [jira] [Updated] (KAFKA-19453) Handle ShareGroupStatePartitionMetadata replay in group coordinator for non-existent groups. Apoorv Mittal (Jira)
• [PR] KAFKA-19453: Ignore group not found in share group record replay. (#2… [kafka] via GitHub
  • Re: [PR] KAFKA-19453: Ignore group not found in share group record replay [kafka] via GitHub
• [PR] KAFKA-18288: Fix Streams CLI describe [kafka] via GitHub
  • Re: [PR] KAFKA-18288: Fix Streams CLI describe [kafka] via GitHub
  • Re: [PR] KAFKA-18288: Fix Streams CLI describe [kafka] via GitHub
  • Re: [PR] KAFKA-18288: Fix Streams CLI describe [kafka] via GitHub
  • Re: [PR] KAFKA-18288: Fix Streams CLI describe [kafka] via GitHub
• [PR] MINOR: Fix build warning in Streams [kafka] via GitHub
  • Re: [PR] MINOR: Fix build warning in Streams [kafka] via GitHub
• [jira] [Updated] (KAFKA-19467) Add a metric for controller thread idleness TengYao Chi (Jira)
  • [jira] [Updated] (KAFKA-19467) Add a metric for controller thread idleness Mahsa Seifikar (Jira)
  • [jira] [Updated] (KAFKA-19467) Add a metric for controller thread idleness Mahsa Seifikar (Jira)
• [jira] [Commented] (KAFKA-19467) Add a metric for controller thread idleness TengYao Chi (Jira)
  • [jira] [Commented] (KAFKA-19467) Add a metric for controller thread idleness Mahsa Seifikar (Jira)
• [PR] MINOR: Cleanups in coordinator-common/group-coordinator [kafka] via GitHub
  • Re: [PR] MINOR: Cleanups in coordinator-common/group-coordinator [kafka] via GitHub
  • Re: [PR] MINOR: Cleanups in coordinator-common/group-coordinator [kafka] via GitHub
  • Re: [PR] MINOR: Cleanups in coordinator-common/group-coordinator [kafka] via GitHub
  • Re: [PR] MINOR: Cleanups in coordinator-common/group-coordinator [kafka] via GitHub
  • Re: [PR] MINOR: Cleanups in coordinator-common/group-coordinator [kafka] via GitHub
  • Re: [PR] MINOR: Cleanups in coordinator-common/group-coordinator [kafka] via GitHub
  • Re: [PR] MINOR: Cleanups in coordinator-common/group-coordinator [kafka] via GitHub
  • Re: [PR] MINOR: Cleanups in coordinator-common/group-coordinator [kafka] via GitHub
• [jira] [Created] (KAFKA-19467) Add a metric for controller thread idleness Mahsa Seifikar (Jira)
• Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub
  • Re: [PR] KAFKA-19357: AsyncConsumer#close hangs during closing because the commitAsync request never completes due to a missing coordinator [kafka] via GitHub

• Earlier messages
• Later messages