jira  

Messages by Thread

• Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
• Re: [PR] KAFKA-20532: Defensive trimming of min.insync.replicas in controller and kafka-topics to tolerate whitespace-contaminated configs [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
• [jira] [Commented] (KAFKA-20734) Offline partition can cause loss of transaction markers Artem Livshits (Jira)
  • [jira] [Commented] (KAFKA-20734) Offline partition can cause loss of transaction markers Shlomit (Jira)
• [jira] [Updated] (KAFKA-20734) Offline partition can cause loss of transaction markers Alyssa Huang (Jira)
  • [jira] [Updated] (KAFKA-20734) Offline partition can cause loss of transaction markers Alyssa Huang (Jira)
• [jira] [Created] (KAFKA-20734) Offline partition can cause loss of transaction markers Alyssa Huang (Jira)
• [PR] MINOR: Update docker_scan supported_image_tag for 4.3.1 [kafka] via GitHub
  • Re: [PR] MINOR: Update docker_scan supported_image_tag for 4.3.1 [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
  • Re: [PR] KAFKA-14648: Do not fail clients if bootstrap servers is not immediately resolvable [kafka] via GitHub
• [PR] Sync 2 recent commits to 4.3 [kafka] via GitHub
  • Re: [PR] Sync 2 recent commits to 4.3 [kafka] via GitHub
• [PR] Sync 2 recent commits to 4.2 [kafka] via GitHub
  • Re: [PR] Sync 2 recent commits to 4.2 [kafka] via GitHub
• [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20579: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
  • Re: [PR] KAFKA-20578: Initial producer incremental allocation for uncompressed data [kafka] via GitHub
• [PR] KAFKA-20498: Add isolation-level reads to RocksDBStore [kafka] via GitHub
  • Re: [PR] KAFKA-20498: Add isolation-level reads to RocksDBStore [kafka] via GitHub
  • Re: [PR] KAFKA-20498: Add isolation-level reads to RocksDBStore [kafka] via GitHub
  • Re: [PR] KAFKA-20498: Add isolation-level reads to RocksDBStore [kafka] via GitHub
  • Re: [PR] KAFKA-20498: Add isolation-level reads to RocksDBStore [kafka] via GitHub
• [PR] KAFKA-20495: Add transactional support to in-memory window and session stores [kafka] via GitHub
  • Re: [PR] KAFKA-20495: Add transactional support to in-memory window and session stores [kafka] via GitHub
  • Re: [PR] KAFKA-20495: Add transactional support to in-memory window and session stores [kafka] via GitHub
  • Re: [PR] KAFKA-20495: Add transactional support to in-memory window and session stores [kafka] via GitHub
  • Re: [PR] KAFKA-20495: Add transactional support to in-memory window and session stores [kafka] via GitHub
  • Re: [PR] KAFKA-20495: Add transactional support to in-memory window and session stores [kafka] via GitHub
  • Re: [PR] KAFKA-20495: Add transactional support to in-memory window and session stores [kafka] via GitHub
  • Re: [PR] KAFKA-20495: Add transactional support to in-memory window and session stores [kafka] via GitHub
  • Re: [PR] KAFKA-20495: Add transactional support to in-memory window and session stores [kafka] via GitHub
  • Re: [PR] KAFKA-20495: Add transactional support to in-memory window and session stores [kafka] via GitHub
• [jira] [Updated] (KAFKA-17164) Consider to enforce application.server <server>:<port> format at config level Matthias J. Sax (Jira)
• [jira] [Resolved] (KAFKA-17164) Consider to enforce application.server <server>:<port> format at config level Matthias J. Sax (Jira)
• [jira] [Updated] (KAFKA-20730) Remove spotless from streams-scala Matthias J. Sax (Jira)
• [jira] [Commented] (KAFKA-20733) KafkaConsumerTest.fetchResponseWithUnexpectedPartitionIsIgnored passes for wrong reason with CONSUMER protocol Lianet Magrans (Jira)
• [PR] KAFKA-20733: Fix fetchResponseWithUnexpectedPartitionIsIgnored passing for wrong reason with CONSUMER protocol [kafka] via GitHub
  • Re: [PR] KAFKA-20733: Fix fetchResponseWithUnexpectedPartitionIsIgnored passing for wrong reason with CONSUMER protocol [kafka] via GitHub
  • Re: [PR] KAFKA-20733: Fix fetchResponseWithUnexpectedPartitionIsIgnored passing for wrong reason with CONSUMER protocol [kafka] via GitHub
  • Re: [PR] KAFKA-20733: Fix fetchResponseWithUnexpectedPartitionIsIgnored passing for wrong reason with CONSUMER protocol [kafka] via GitHub
• Re: [PR] KAFKA-20259: Verify IQv1 and IQv2 do not break with headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20259: Verify IQv1 and IQv2 do not break with headers-aware state stores [kafka] via GitHub
• [PR] MINOR: Merge kafka.security classes into test-common [kafka] via GitHub
• [jira] [Updated] (KAFKA-20197) Add headers support to StreamPartitioner Uladzislau Blok (Jira)
• [jira] [Created] (KAFKA-20733) KafkaConsumerTest.fetchResponseWithUnexpectedPartitionIsIgnored passes for wrong reason with CONSUMER protocol Jiwon Park (Jira)
• Re: [PR] KAFKA-19193: trace-log rack-specific load stats in rack-aware mode [kafka] via GitHub
• Re: [PR] KAFKA-19193: throw ConfigException if rack is empty in rack-aware mode [kafka] via GitHub
• Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-20197: Headers aware StreamPartitioner [kafka] via GitHub
• Re: [PR] KAFKA-17840: Move ClientRequestQuotaManager to server module [kafka] via GitHub
  • Re: [PR] KAFKA-17840: Move ClientRequestQuotaManager to server module [kafka] via GitHub
• Re: [PR] KAFKA-20645: Move LogLoaderTest to storage module [kafka] via GitHub
  • Re: [PR] KAFKA-20645: Move LogLoaderTest to storage module [kafka] via GitHub
• [jira] [Commented] (KAFKA-20731) Streams: transitToUpdateStandby is called without checking ACTIVE_RESTORING, crashing the state updater thread Eswarar Siva (Jira)
  • [jira] [Commented] (KAFKA-20731) Streams: transitToUpdateStandby is called without checking ACTIVE_RESTORING, crashing the state updater thread Nikita Shupletsov (Jira)
  • [jira] [Commented] (KAFKA-20731) Streams: transitToUpdateStandby is called without checking ACTIVE_RESTORING, crashing the state updater thread Lucas Brutschy (Jira)
  • [jira] [Commented] (KAFKA-20731) Streams: transitToUpdateStandby is called without checking ACTIVE_RESTORING, crashing the state updater thread Wang Xiaoqing (Jira)
  • [jira] [Commented] (KAFKA-20731) Streams: transitToUpdateStandby is called without checking ACTIVE_RESTORING, crashing the state updater thread Nikita Shupletsov (Jira)
• [jira] [Resolved] (KAFKA-20524) Initialization of share group offsets from a specific offset or a file Andrew Schofield (Jira)
• [jira] [Assigned] (KAFKA-20724) Topology pausing may have race condition Eswarar Siva (Jira)
• [PR] KAFKA-20724: prevent duplicate task in tasks() during pause and resume [kafka] via GitHub
  • Re: [PR] KAFKA-20724: prevent duplicate task in tasks() during pause and resume [kafka] via GitHub
  • Re: [PR] KAFKA-20724: prevent duplicate task in tasks() during pause and resume [kafka] via GitHub
• Re: [PR] KAFKA-20223: Extended I/O Metrics Collection [kafka] via GitHub
  • Re: [PR] KAFKA-20223: Extended I/O Metrics Collection [kafka] via GitHub
  • Re: [PR] KAFKA-20223: Extended I/O Metrics Collection [kafka] via GitHub
  • Re: [PR] KAFKA-20223: Extended I/O Metrics Collection [kafka] via GitHub
  • Re: [PR] KAFKA-20223: Extended I/O Metrics Collection [kafka] via GitHub
  • Re: [PR] KAFKA-20223: Extended I/O Metrics Collection [kafka] via GitHub
  • Re: [PR] KAFKA-20223: Extended I/O Metrics Collection [kafka] via GitHub
• [jira] [Updated] (KAFKA-20732) Data loss: tiered size-retention deletes in-retention data from both tiers after leader election when highestOffsetInRemoteStorage is unset (-1) Adam Horky (Jira)
  • [jira] [Updated] (KAFKA-20732) Data loss: tiered size-retention deletes in-retention data from both tiers after leader election when highestOffsetInRemoteStorage is unset (-1) Adam Horky (Jira)
• [jira] [Created] (KAFKA-20732) Data loss: tiered size-retention deletes in-retention data from both tiers after leader election when highestOffsetInRemoteStorage is unset (-1) Adam Horky (Jira)
• [PR] KAFKA-20490: Replace txn buffer skip-list with TreeMap [kafka] via GitHub
  • Re: [PR] KAFKA-20490: Replace txn buffer skip-list with TreeMap [kafka] via GitHub
  • Re: [PR] KAFKA-20490: Replace txn buffer skip-list with TreeMap [kafka] via GitHub
  • Re: [PR] KAFKA-20490: Replace txn buffer skip-list with TreeMap [kafka] via GitHub
  • Re: [PR] KAFKA-20490: Replace txn buffer skip-list with TreeMap [kafka] via GitHub
  • Re: [PR] KAFKA-20490: Replace txn buffer skip-list with TreeMap [kafka] via GitHub
• [jira] [Commented] (KAFKA-20608) classic consumer static member rejoin can fail with GroupMaxSizeReachedException at max size Nilesh Kumar (Jira)
• [jira] [Updated] (KAFKA-20731) Streams: transitToUpdateStandby is called without checking ACTIVE_RESTORING, crashing the state updater thread Eswarar Siva (Jira)
• [jira] [Comment Edited] (KAFKA-20721) Streams: "Task not found in the state updater. This indicates a bug." after a state updater remove times out during cold start rebalancing Eswarar Siva (Jira)
  • [jira] [Comment Edited] (KAFKA-20721) Streams: "Task not found in the state updater. This indicates a bug." after a state updater remove times out during cold start rebalancing Nikita Shupletsov (Jira)
  • [jira] [Comment Edited] (KAFKA-20721) Streams: "Task not found in the state updater. This indicates a bug." after a state updater remove times out during cold start rebalancing Nikita Shupletsov (Jira)
• [jira] [Created] (KAFKA-20731) Streams: transitToUpdateStandby is called without checking ACTIVE_RESTORING, crashing the state updater thread Eswarar Siva (Jira)
• [jira] [Resolved] (KAFKA-20729) RocksDBTransactionBuffer missing newBaseSnapshotIterator breaks trunk compile Nilesh Kumar (Jira)
• Re: [PR] KAFKA-19193: add Javadoc for rack-aware params in BuiltInPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-19193: add Javadoc for rack-aware params in BuiltInPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-19193: add Javadoc for rack-aware params in BuiltInPartitioner [kafka] via GitHub
  • Re: [PR] KAFKA-19193: add Javadoc for rack-aware params in BuiltInPartitioner [kafka] via GitHub
• [jira] [Commented] (KAFKA-20721) Streams: "Task not found in the state updater. This indicates a bug." after a state updater remove times out during cold start rebalancing Lucas Brutschy (Jira)
  • [jira] [Commented] (KAFKA-20721) Streams: "Task not found in the state updater. This indicates a bug." after a state updater remove times out during cold start rebalancing Eswarar Siva (Jira)
  • [jira] [Commented] (KAFKA-20721) Streams: "Task not found in the state updater. This indicates a bug." after a state updater remove times out during cold start rebalancing Nikita Shupletsov (Jira)
  • [jira] [Commented] (KAFKA-20721) Streams: "Task not found in the state updater. This indicates a bug." after a state updater remove times out during cold start rebalancing Lucas Brutschy (Jira)
  • [jira] [Commented] (KAFKA-20721) Streams: "Task not found in the state updater. This indicates a bug." after a state updater remove times out during cold start rebalancing Nikita Shupletsov (Jira)
• [PR] KAFKA-20686: Add base integ tests for share group DLQ. [1/N] [kafka] via GitHub
  • Re: [PR] KAFKA-20686: Add base integ tests for share group DLQ. [1/N] [kafka] via GitHub
  • Re: [PR] KAFKA-20686: Add base integ tests for share group DLQ. [1/N] [kafka] via GitHub
• [jira] [Updated] (KAFKA-20721) Streams: "Task not found in the state updater. This indicates a bug." after a state updater remove times out during cold start rebalancing Lucas Brutschy (Jira)
• [jira] [Resolved] (KAFKA-20601) ConsumerGroup static member rejoin can fail with GroupMaxSizeReachedException at max size David Jacot (Jira)
• [jira] [Resolved] (KAFKA-20662) Proper error code for malformed request during online migration David Jacot (Jira)
• Re: [PR] KAFKA-20662: Throw `INCONSISTENT_GROUP_PROTOCOL` for malformed request during online migration [kafka] via GitHub
  • Re: [PR] KAFKA-20662: Throw `INCONSISTENT_GROUP_PROTOCOL` for malformed request during online migration [kafka] via GitHub
  • [PR] KAFKA-20662: Throw `INCONSISTENT_GROUP_PROTOCOL` for malformed request during online migration [kafka] via GitHub
  • Re: [PR] KAFKA-20662: Throw `INCONSISTENT_GROUP_PROTOCOL` for malformed request during online migration [kafka] via GitHub
• [PR] HOTFIX: fix compilation error [kafka] via GitHub
  • Re: [PR] HOTFIX: fix compilation error [kafka] via GitHub
• [PR] KAFKA-20116: Send task-(end)-offset only if changed (5/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Send task-(end)-offset only if changed (5/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Send task-(end)-offset only if changed (5/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Send task-(end)-offset only if changed (5/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Send task-(end)-offset only if changed (5/N) [kafka] via GitHub

• Earlier messages
• Later messages