[jira] [Resolved] (KAFKA-6362) auto commit not work since coordinatorUnknown() is always true.

[ https://issues.apache.org/jira/browse/KAFKA-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6362. Resolution: Fixed Fix Version/s: 1.1.0 > auto commit not work since coordinatorUnknow

[jira] [Resolved] (KAFKA-6501) Add test to verify markPartitionsForTruncation after fetcher thread pool resize

[ https://issues.apache.org/jira/browse/KAFKA-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6501. Resolution: Fixed Fix Version/s: (was: 1.2.0) 1.1.0 > Add test

[jira] [Resolved] (KAFKA-6511) Connect header parser incorrectly parses arrays

[ https://issues.apache.org/jira/browse/KAFKA-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6511. Resolution: Fixed > Connect header parser incorrectly parses arrays > --

[jira] [Resolved] (KAFKA-4221) KafkaConsumer Fetcher can send ListOffsets requests in parallel when initializing position

[ https://issues.apache.org/jira/browse/KAFKA-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4221. Resolution: Fixed > KafkaConsumer Fetcher can send ListOffsets requests in parallel when >

[jira] [Resolved] (KAFKA-4221) KafkaConsumer Fetcher can send ListOffsets requests in parallel when initializing position

[ https://issues.apache.org/jira/browse/KAFKA-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4221. Resolution: Duplicate > KafkaConsumer Fetcher can send ListOffsets requests in parallel when

[jira] [Reopened] (KAFKA-4221) KafkaConsumer Fetcher can send ListOffsets requests in parallel when initializing position

[ https://issues.apache.org/jira/browse/KAFKA-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reopened KAFKA-4221: > KafkaConsumer Fetcher can send ListOffsets requests in parallel when > initializing position

[jira] [Resolved] (KAFKA-5996) JsonConverter generates "Mismatching schema" DataException

[ https://issues.apache.org/jira/browse/KAFKA-5996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5996. Resolution: Fixed Fix Version/s: 1.0.2 1.1.0 > JsonConverter gener

[jira] [Resolved] (KAFKA-6541) StackOverflow exceptions in thread 'kafka-coordinator-heartbeat-thread

[ https://issues.apache.org/jira/browse/KAFKA-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6541. Resolution: Duplicate Closing as duplicate for now. Please reopen if you think the issue has

[jira] [Resolved] (KAFKA-5430) new consumers getting data for revoked partitions

[ https://issues.apache.org/jira/browse/KAFKA-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5430. Resolution: Fixed I think this issue was fixed in KAFKA-5154. Please reopen if you think it

[jira] [Resolved] (KAFKA-6568) LogCleanerManager.doneDeleting() should check the partition state before deleting the in progress partition

[ https://issues.apache.org/jira/browse/KAFKA-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6568. Resolution: Fixed Fix Version/s: 1.0.2 0.11.0.3 > LogCleanerManage

[jira] [Reopened] (KAFKA-6238) Issues with protocol version when applying a rolling upgrade to 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reopened KAFKA-6238: Reopening this since there is a bug in the config validation. > Issues with protocol version wh

[jira] [Resolved] (KAFKA-6099) Seeking consumer to evicted offset resets the offset

[ https://issues.apache.org/jira/browse/KAFKA-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6099. Resolution: Not A Problem As pointed out by [~tomas.kralik], you should use auto.reset.polic

[jira] [Resolved] (KAFKA-5624) Unsafe use of expired sensors

[ https://issues.apache.org/jira/browse/KAFKA-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5624. Resolution: Fixed Fix Version/s: 2.0.0 > Unsafe use of expired sensors >

[jira] [Resolved] (KAFKA-6554) Broker doesn't reject Produce request with inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-6554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6554. Resolution: Fixed Fix Version/s: 1.1.0 > Broker doesn't reject Produce request with i

[jira] [Resolved] (KAFKA-6573) KafkaController.brokerInfo not updated on dynamic update

[ https://issues.apache.org/jira/browse/KAFKA-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6573. Resolution: Fixed > KafkaController.brokerInfo not updated on dynamic update > -

[jira] [Resolved] (KAFKA-6578) Connect distributed and standalone worker 'main()' methods should catch and log all exceptions

[ https://issues.apache.org/jira/browse/KAFKA-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6578. Resolution: Fixed Fix Version/s: 1.1.0 > Connect distributed and standalone worker 'm

[jira] [Created] (KAFKA-6590) Consumer bytes-fetched and records-fetched are not aggregated correctly

Jason Gustafson created KAFKA-6590: -- Summary: Consumer bytes-fetched and records-fetched are not aggregated correctly Key: KAFKA-6590 URL: https://issues.apache.org/jira/browse/KAFKA-6590 Project: Ka

[jira] [Resolved] (KAFKA-3744) Message format needs to identify serializer

[ https://issues.apache.org/jira/browse/KAFKA-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3744. Resolution: Won't Fix Closing this as "won't fix" since Kafka now supports message headers f

[jira] [Resolved] (KAFKA-6196) Kafka Transactional producer with broker on windows

[ https://issues.apache.org/jira/browse/KAFKA-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6196. Resolution: Duplicate Thanks for the patch. Marking this as a dup since it seems to be the s

[jira] [Resolved] (KAFKA-6153) Kafka Transactional Messaging does not work on windows but on linux

[ https://issues.apache.org/jira/browse/KAFKA-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6153. Resolution: Duplicate Seems like the same underlying issue as KAFKA-6052. Marking as dup for

[jira] [Resolved] (KAFKA-6076) Using new producer api of transaction twice failed when server run on Windows OS

[ https://issues.apache.org/jira/browse/KAFKA-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6076. Resolution: Duplicate Marking as dup of KAFKA-6052 since it is likely the same underlying ca

[jira] [Resolved] (KAFKA-5327) Console Consumer should only poll for up to max messages

[ https://issues.apache.org/jira/browse/KAFKA-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5327. Resolution: Fixed > Console Consumer should only poll for up to max messages > -

[jira] [Created] (KAFKA-6593) Coordinator disconnect in heartbeat thread can cause commitSync to block indefinitely

Jason Gustafson created KAFKA-6593: -- Summary: Coordinator disconnect in heartbeat thread can cause commitSync to block indefinitely Key: KAFKA-6593 URL: https://issues.apache.org/jira/browse/KAFKA-6593

[jira] [Resolved] (KAFKA-6593) Coordinator disconnect in heartbeat thread can cause commitSync to block indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-6593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6593. Resolution: Fixed > Coordinator disconnect in heartbeat thread can cause commitSync to block

[jira] [Resolved] (KAFKA-3513) Transient failure of OffsetValidationTest

[ https://issues.apache.org/jira/browse/KAFKA-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3513. Resolution: Fixed We haven't seen this in some time, so I'm going to close this. We can reop

[jira] [Created] (KAFKA-6606) Regression in consumer auto-commit backoff behavior

Jason Gustafson created KAFKA-6606: -- Summary: Regression in consumer auto-commit backoff behavior Key: KAFKA-6606 URL: https://issues.apache.org/jira/browse/KAFKA-6606 Project: Kafka Issue T

[jira] [Created] (KAFKA-6609) Offset commit reordering possible on coordinator disconnect

Jason Gustafson created KAFKA-6609: -- Summary: Offset commit reordering possible on coordinator disconnect Key: KAFKA-6609 URL: https://issues.apache.org/jira/browse/KAFKA-6609 Project: Kafka

[jira] [Resolved] (KAFKA-6606) Regression in consumer auto-commit backoff behavior

[ https://issues.apache.org/jira/browse/KAFKA-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6606. Resolution: Fixed Note this issue did not affect any released version. > Regression in cons

[jira] [Resolved] (KAFKA-6610) initial high watermark -1, used for truncation, cause "Cannot truncate to a negative offset"

[ https://issues.apache.org/jira/browse/KAFKA-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6610. Resolution: Duplicate Thanks for the report. This looks like KAFKA-3978. We are still not su

[jira] [Resolved] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3806. Resolution: Fixed Assignee: Ewen Cheslack-Postava > Adjust default values of log.reten

[jira] [Created] (KAFKA-6615) Add scripts for DumpLogSegments

Jason Gustafson created KAFKA-6615: -- Summary: Add scripts for DumpLogSegments Key: KAFKA-6615 URL: https://issues.apache.org/jira/browse/KAFKA-6615 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-6615) Add scripts for DumpLogSegments

[ https://issues.apache.org/jira/browse/KAFKA-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6615. Resolution: Fixed Fix Version/s: 1.2.0 > Add scripts for DumpLogSegments > --

[jira] [Created] (KAFKA-6623) Consider renaming inefficient RecordBatch operations

Jason Gustafson created KAFKA-6623: -- Summary: Consider renaming inefficient RecordBatch operations Key: KAFKA-6623 URL: https://issues.apache.org/jira/browse/KAFKA-6623 Project: Kafka Issue

[jira] [Created] (KAFKA-6627) Console producer default config values override explicitly provided properties

Jason Gustafson created KAFKA-6627: -- Summary: Console producer default config values override explicitly provided properties Key: KAFKA-6627 URL: https://issues.apache.org/jira/browse/KAFKA-6627 Proj

[jira] [Resolved] (KAFKA-6622) GroupMetadataManager.loadGroupsAndOffsets decompresses record batch needlessly

[ https://issues.apache.org/jira/browse/KAFKA-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6622. Resolution: Fixed Fix Version/s: 1.1.0 > GroupMetadataManager.loadGroupsAndOffsets de

[jira] [Created] (KAFKA-6635) Producer close does not await pending transaction

Jason Gustafson created KAFKA-6635: -- Summary: Producer close does not await pending transaction Key: KAFKA-6635 URL: https://issues.apache.org/jira/browse/KAFKA-6635 Project: Kafka Issue Typ

[jira] [Created] (KAFKA-6639) Follower may have sparse index if catching up

Jason Gustafson created KAFKA-6639: -- Summary: Follower may have sparse index if catching up Key: KAFKA-6639 URL: https://issues.apache.org/jira/browse/KAFKA-6639 Project: Kafka Issue Type: B

[jira] [Resolved] (KAFKA-3368) Add the Message/Record set protocol to the protocol docs

[ https://issues.apache.org/jira/browse/KAFKA-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3368. Resolution: Fixed Fix Version/s: 1.2.0 > Add the Message/Record set protocol to the p

[jira] [Resolved] (KAFKA-6024) Consider moving validation in KafkaConsumer ahead of call to acquireAndEnsureOpen()

[ https://issues.apache.org/jira/browse/KAFKA-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6024. Resolution: Fixed Fix Version/s: 1.2.0 > Consider moving validation in KafkaConsumer

[jira] [Resolved] (KAFKA-3978) Cannot truncate to a negative offset (-1) exception at broker startup

[ https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3978. Resolution: Fixed Fix Version/s: 1.2.0 > Cannot truncate to a negative offset (-1) ex

[jira] [Created] (KAFKA-6656) Use non-zero status code when kafka-configs.sh fails

Jason Gustafson created KAFKA-6656: -- Summary: Use non-zero status code when kafka-configs.sh fails Key: KAFKA-6656 URL: https://issues.apache.org/jira/browse/KAFKA-6656 Project: Kafka Issue

[jira] [Resolved] (KAFKA-6640) Improve efficiency of KafkaAdminClient.describeTopics()

[ https://issues.apache.org/jira/browse/KAFKA-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6640. Resolution: Fixed Fix Version/s: 1.2.0 > Improve efficiency of KafkaAdminClient.descr

[jira] [Resolved] (KAFKA-6653) Delayed operations may not be completed when there is lock contention

[ https://issues.apache.org/jira/browse/KAFKA-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6653. Resolution: Fixed Fix Version/s: 1.1.0 > Delayed operations may not be completed when

[jira] [Resolved] (KAFKA-6656) Use non-zero status code when kafka-configs.sh fails

[ https://issues.apache.org/jira/browse/KAFKA-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6656. Resolution: Fixed Fix Version/s: 1.2.0 > Use non-zero status code when kafka-configs.

[jira] [Created] (KAFKA-6672) ConfigCommand failing to alter configs

Jason Gustafson created KAFKA-6672: -- Summary: ConfigCommand failing to alter configs Key: KAFKA-6672 URL: https://issues.apache.org/jira/browse/KAFKA-6672 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-6658) Fix RoundTripWorkload and make k/v generation configurable

[ https://issues.apache.org/jira/browse/KAFKA-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6658. Resolution: Fixed Fix Version/s: 1.2.0 > Fix RoundTripWorkload and make k/v generatio

[jira] [Resolved] (KAFKA-6672) ConfigCommand failing to alter configs

[ https://issues.apache.org/jira/browse/KAFKA-6672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6672. Resolution: Fixed Fix Version/s: 1.2.0 > ConfigCommand failing to alter configs > ---

[jira] [Resolved] (KAFKA-6530) Use actual first offset of messages when rolling log segment for magic v2

[ https://issues.apache.org/jira/browse/KAFKA-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6530. Resolution: Fixed Fix Version/s: 1.2.0 > Use actual first offset of messages when rol

[jira] [Resolved] (KAFKA-6637) if set topic config segment.ms=0 Kafka broker won't be able to start

[ https://issues.apache.org/jira/browse/KAFKA-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6637. Resolution: Fixed Fix Version/s: 1.2.0 > if set topic config segment.ms=0 Kafka broke

[jira] [Resolved] (KAFKA-6446) KafkaProducer with transactionId endless waits when bootstrap server is down

[ https://issues.apache.org/jira/browse/KAFKA-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6446. Resolution: Fixed Fix Version/s: 1.2.0 > KafkaProducer with transactionId endless wai

[jira] [Resolved] (KAFKA-6724) ConsumerPerformance resets offsets on every startup

[ https://issues.apache.org/jira/browse/KAFKA-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6724. Resolution: Fixed Fix Version/s: 1.2.0 > ConsumerPerformance resets offsets on every

[jira] [Resolved] (KAFKA-6739) Broker receives error when handling request with java.lang.IllegalArgumentException: Magic v0 does not support record headers

[ https://issues.apache.org/jira/browse/KAFKA-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6739. Resolution: Fixed Fix Version/s: 1.0.2 > Broker receives error when handling request

[jira] [Created] (KAFKA-6751) Make max.connections.per.ip.overrides a dynamic config

Jason Gustafson created KAFKA-6751: -- Summary: Make max.connections.per.ip.overrides a dynamic config Key: KAFKA-6751 URL: https://issues.apache.org/jira/browse/KAFKA-6751 Project: Kafka Issu

[jira] [Created] (KAFKA-6752) Unclean leader election metric no longer working

Jason Gustafson created KAFKA-6752: -- Summary: Unclean leader election metric no longer working Key: KAFKA-6752 URL: https://issues.apache.org/jira/browse/KAFKA-6752 Project: Kafka Issue Type

[jira] [Created] (KAFKA-6768) Producer may hang in close with pending transaction

Jason Gustafson created KAFKA-6768: -- Summary: Producer may hang in close with pending transaction Key: KAFKA-6768 URL: https://issues.apache.org/jira/browse/KAFKA-6768 Project: Kafka Issue T

[jira] [Resolved] (KAFKA-6768) Producer may hang in close with pending transaction

[ https://issues.apache.org/jira/browse/KAFKA-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6768. Resolution: Fixed > Producer may hang in close with pending transaction > --

[jira] [Created] (KAFKA-6774) Improve default groupId behavior in consumer

Jason Gustafson created KAFKA-6774: -- Summary: Improve default groupId behavior in consumer Key: KAFKA-6774 URL: https://issues.apache.org/jira/browse/KAFKA-6774 Project: Kafka Issue Type: Im

[jira] [Resolved] (KAFKA-6773) Kafka consumer without group.id crashes when requesting offset on a topic-partition

[ https://issues.apache.org/jira/browse/KAFKA-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6773. Resolution: Fixed Fix Version/s: (was: 1.1.1) (was: 1.2.0)

[jira] [Created] (KAFKA-6781) Transient failure in KafkaAdminClientTest.testDescribeConsumerGroupOffsets

Jason Gustafson created KAFKA-6781: -- Summary: Transient failure in KafkaAdminClientTest.testDescribeConsumerGroupOffsets Key: KAFKA-6781 URL: https://issues.apache.org/jira/browse/KAFKA-6781 Project:

[jira] [Created] (KAFKA-6794) Support for incremental replica reassignment

Jason Gustafson created KAFKA-6794: -- Summary: Support for incremental replica reassignment Key: KAFKA-6794 URL: https://issues.apache.org/jira/browse/KAFKA-6794 Project: Kafka Issue Type: Im

[jira] [Resolved] (KAFKA-6514) Add API version as a tag for the RequestsPerSec metric

[ https://issues.apache.org/jira/browse/KAFKA-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6514. Resolution: Fixed Fix Version/s: 1.2.0 > Add API version as a tag for the RequestsPer

[jira] [Created] (KAFKA-6796) Surprising UNKNOWN_TOPIC error for produce/fetch requests to non-replicas

Jason Gustafson created KAFKA-6796: -- Summary: Surprising UNKNOWN_TOPIC error for produce/fetch requests to non-replicas Key: KAFKA-6796 URL: https://issues.apache.org/jira/browse/KAFKA-6796 Project:

[jira] [Resolved] (KAFKA-6770) 1.1.0 New Protocol Versions section in doc is empty

[ https://issues.apache.org/jira/browse/KAFKA-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6770. Resolution: Fixed > 1.1.0 New Protocol Versions section in doc is empty > --

[jira] [Resolved] (KAFKA-3365) Add a documentation field for types and update doc generation

[ https://issues.apache.org/jira/browse/KAFKA-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3365. Resolution: Fixed > Add a documentation field for types and update doc generation >

[jira] [Resolved] (KAFKA-6778) DescribeConfigs does not return error for non-existent topic

[ https://issues.apache.org/jira/browse/KAFKA-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6778. Resolution: Fixed Fix Version/s: 2.0.0 > DescribeConfigs does not return error for no

[jira] [Resolved] (KAFKA-6810) Enable dynamic reconfiguration of SSL truststores

[ https://issues.apache.org/jira/browse/KAFKA-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6810. Resolution: Fixed > Enable dynamic reconfiguration of SSL truststores >

[jira] [Resolved] (KAFKA-6854) Log cleaner fails with transaction markers that are deleted during clean

[ https://issues.apache.org/jira/browse/KAFKA-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6854. Resolution: Fixed > Log cleaner fails with transaction markers that are deleted during clean

[jira] [Resolved] (KAFKA-6751) Make max.connections.per.ip.overrides a dynamic config

[ https://issues.apache.org/jira/browse/KAFKA-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6751. Resolution: Fixed > Make max.connections.per.ip.overrides a dynamic config > --

[jira] [Resolved] (KAFKA-7140) Remove deprecated poll usages

[ https://issues.apache.org/jira/browse/KAFKA-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7140. Resolution: Fixed > Remove deprecated poll usages > - > >

[jira] [Resolved] (KAFKA-7164) Follower should truncate after every leader epoch change

[ https://issues.apache.org/jira/browse/KAFKA-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7164. Resolution: Fixed Fix Version/s: 2.1.0 2.0.1 1.

[jira] [Created] (KAFKA-7296) Producer should handler COORDINATOR_LOADING error in TxnOffsetCommit

Jason Gustafson created KAFKA-7296: -- Summary: Producer should handler COORDINATOR_LOADING error in TxnOffsetCommit Key: KAFKA-7296 URL: https://issues.apache.org/jira/browse/KAFKA-7296 Project: Kafka

[jira] [Created] (KAFKA-7298) Concurrent DeleteRecords can lead to fatal OutOfSequence error in producer

Jason Gustafson created KAFKA-7298: -- Summary: Concurrent DeleteRecords can lead to fatal OutOfSequence error in producer Key: KAFKA-7298 URL: https://issues.apache.org/jira/browse/KAFKA-7298 Project:

[jira] [Resolved] (KAFKA-7296) Producer should handle COORDINATOR_LOADING error in TxnOffsetCommit

[ https://issues.apache.org/jira/browse/KAFKA-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7296. Resolution: Fixed > Producer should handle COORDINATOR_LOADING error in TxnOffsetCommit > -

[jira] [Resolved] (KAFKA-7298) Concurrent DeleteRecords can lead to fatal OutOfSequence error in producer

[ https://issues.apache.org/jira/browse/KAFKA-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7298. Resolution: Fixed Fix Version/s: 2.0.1 > Concurrent DeleteRecords can lead to fatal

[jira] [Resolved] (KAFKA-7278) replaceSegments() should not call asyncDeleteSegment() for segments which have been removed from segments list

[ https://issues.apache.org/jira/browse/KAFKA-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7278. Resolution: Fixed Fix Version/s: 2.0.1 > replaceSegments() should not call asyncDele

[jira] [Resolved] (KAFKA-5891) Cast transformation fails if record schema contains timestamp field

[ https://issues.apache.org/jira/browse/KAFKA-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5891. Resolution: Fixed Fix Version/s: 2.0.1 1.1.2 1.

[jira] [Created] (KAFKA-7333) Protocol changes for KIP-320

Jason Gustafson created KAFKA-7333: -- Summary: Protocol changes for KIP-320 Key: KAFKA-7333 URL: https://issues.apache.org/jira/browse/KAFKA-7333 Project: Kafka Issue Type: Bug Re

[jira] [Created] (KAFKA-7335) Store clusterId locally to ensure broker joins the right cluster

Jason Gustafson created KAFKA-7335: -- Summary: Store clusterId locally to ensure broker joins the right cluster Key: KAFKA-7335 URL: https://issues.apache.org/jira/browse/KAFKA-7335 Project: Kafka

[jira] [Resolved] (KAFKA-7139) Support to exclude the internal topics in kafka-topics.sh command

[ https://issues.apache.org/jira/browse/KAFKA-7139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7139. Resolution: Fixed Fix Version/s: 2.1.0 > Support to exclude the internal topics in k

[jira] [Created] (KAFKA-7347) Wrong error code returned for OffsetsForLeaderEpoch from follower/non-replica

Jason Gustafson created KAFKA-7347: -- Summary: Wrong error code returned for OffsetsForLeaderEpoch from follower/non-replica Key: KAFKA-7347 URL: https://issues.apache.org/jira/browse/KAFKA-7347 Proje

[jira] [Resolved] (KAFKA-7347) Wrong error code returned for OffsetsForLeaderEpoch from non-replica

[ https://issues.apache.org/jira/browse/KAFKA-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7347. Resolution: Fixed Fix Version/s: 2.1.0 > Wrong error code returned for OffsetsForLea

[jira] [Resolved] (KAFKA-7128) Lagging high watermark can lead to committed data loss after ISR expansion

[ https://issues.apache.org/jira/browse/KAFKA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7128. Resolution: Fixed Fix Version/s: 2.1.0 2.0.1 1.

[jira] [Created] (KAFKA-7369) Retry when possible in AdminClient.listConsumerGroups

Jason Gustafson created KAFKA-7369: -- Summary: Retry when possible in AdminClient.listConsumerGroups Key: KAFKA-7369 URL: https://issues.apache.org/jira/browse/KAFKA-7369 Project: Kafka Issue

[jira] [Resolved] (KAFKA-7369) Retry when possible in AdminClient.listConsumerGroups

[ https://issues.apache.org/jira/browse/KAFKA-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7369. Resolution: Fixed Fix Version/s: 2.1.0 2.0.1 > Retry when possibl

[jira] [Created] (KAFKA-7383) Verify leader epoch in produce requests (KIP-359)

Jason Gustafson created KAFKA-7383: -- Summary: Verify leader epoch in produce requests (KIP-359) Key: KAFKA-7383 URL: https://issues.apache.org/jira/browse/KAFKA-7383 Project: Kafka Issue Typ

[jira] [Resolved] (KAFKA-7385) Log cleaner crashes when empty batches are retained with idempotent or transactional producers

[ https://issues.apache.org/jira/browse/KAFKA-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7385. Resolution: Fixed Fix Version/s: 2.0.1 > Log cleaner crashes when empty batches are

[jira] [Resolved] (KAFKA-7286) Loading offsets and group metadata hangs with large group metadata records

[ https://issues.apache.org/jira/browse/KAFKA-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7286. Resolution: Fixed Fix Version/s: 2.1.0 > Loading offsets and group metadata hangs wi

[jira] [Created] (KAFKA-7394) Allow OffsetsForLeaderEpoch requests with topic describe ACL (KIP-320)

Jason Gustafson created KAFKA-7394: -- Summary: Allow OffsetsForLeaderEpoch requests with topic describe ACL (KIP-320) Key: KAFKA-7394 URL: https://issues.apache.org/jira/browse/KAFKA-7394 Project: Kaf

[jira] [Created] (KAFKA-7395) Add fencing to OffsetsForLeaderEpoch API (KIP-320)

Jason Gustafson created KAFKA-7395: -- Summary: Add fencing to OffsetsForLeaderEpoch API (KIP-320) Key: KAFKA-7395 URL: https://issues.apache.org/jira/browse/KAFKA-7395 Project: Kafka Issue Ty

[jira] [Resolved] (KAFKA-7044) kafka-consumer-groups.sh NullPointerException describing round robin or sticky assignors

[ https://issues.apache.org/jira/browse/KAFKA-7044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7044. Resolution: Fixed Fix Version/s: 2.0.1 1.1.2 > kafka-consumer-gro

[jira] [Resolved] (KAFKA-7394) Allow OffsetsForLeaderEpoch requests with topic describe ACL (KIP-320)

[ https://issues.apache.org/jira/browse/KAFKA-7394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7394. Resolution: Fixed Fix Version/s: 2.1.0 > Allow OffsetsForLeaderEpoch requests with t

[jira] [Created] (KAFKA-7408) Truncate to LSO on unclean leader election

Jason Gustafson created KAFKA-7408: -- Summary: Truncate to LSO on unclean leader election Key: KAFKA-7408 URL: https://issues.apache.org/jira/browse/KAFKA-7408 Project: Kafka Issue Type: Impr

[jira] [Created] (KAFKA-7409) Validate topic configs prior to topic creation

Jason Gustafson created KAFKA-7409: -- Summary: Validate topic configs prior to topic creation Key: KAFKA-7409 URL: https://issues.apache.org/jira/browse/KAFKA-7409 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-7414) Do not fail broker on out of range offsets in replica fetcher

Jason Gustafson created KAFKA-7414: -- Summary: Do not fail broker on out of range offsets in replica fetcher Key: KAFKA-7414 URL: https://issues.apache.org/jira/browse/KAFKA-7414 Project: Kafka

[jira] [Resolved] (KAFKA-7280) ConcurrentModificationException in FetchSessionHandler in heartbeat thread

[ https://issues.apache.org/jira/browse/KAFKA-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7280. Resolution: Fixed Fix Version/s: (was: 1.1.2) > ConcurrentModificationException

[jira] [Resolved] (KAFKA-7414) Do not fail broker on out of range offsets in replica fetcher

[ https://issues.apache.org/jira/browse/KAFKA-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7414. Resolution: Fixed Fix Version/s: 2.1.0 > Do not fail broker on out of range offsets

[jira] [Resolved] (KAFKA-7150) Error in processing fetched data for one partition may stop follower fetching other partitions

[ https://issues.apache.org/jira/browse/KAFKA-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7150. Resolution: Not A Problem This is no longer a problem since we have removed the logic to ra

[jira] [Resolved] (KAFKA-6923) Consolidate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

[ https://issues.apache.org/jira/browse/KAFKA-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6923. Resolution: Fixed > Consolidate ExtendedSerializer/Serializer and > ExtendedDeserializer/D

[jira] [Created] (KAFKA-7437) Store leader epoch in offset commit metadata

Jason Gustafson created KAFKA-7437: -- Summary: Store leader epoch in offset commit metadata Key: KAFKA-7437 URL: https://issues.apache.org/jira/browse/KAFKA-7437 Project: Kafka Issue Type: Im

[jira] [Resolved] (KAFKA-7403) Offset commit failure after upgrading brokers past KIP-211/KAFKA-4682

[ https://issues.apache.org/jira/browse/KAFKA-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7403. Resolution: Fixed > Offset commit failure after upgrading brokers past KIP-211/KAFKA-4682 >

<    1   2   3   4   5   6   7   8   9   10   >