[jira] [Created] (KAFKA-9947) TransactionsBounceTest may leave threads running

Jason Gustafson created KAFKA-9947: -- Summary: TransactionsBounceTest may leave threads running Key: KAFKA-9947 URL: https://issues.apache.org/jira/browse/KAFKA-9947 Project: Kafka Issue

[jira] [Updated] (KAFKA-9939) Fetch request metrics are updated twice for delayed fetches

[ https://issues.apache.org/jira/browse/KAFKA-9939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9939: --- Affects Version/s: 2.5.0 > Fetch request metrics are updated twice for delayed fetches >

[jira] [Resolved] (KAFKA-9939) Fetch request metrics are updated twice for delayed fetches

[ https://issues.apache.org/jira/browse/KAFKA-9939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9939. Fix Version/s: 2.6.0 Resolution: Fixed > Fetch request metrics are updated twice

[jira] [Resolved] (KAFKA-9543) Consumer offset reset after new segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9543. Fix Version/s: 2.5.1 2.4.2 Resolution: Fixed > Consumer offset

[jira] [Updated] (KAFKA-9543) Consumer offset reset after new segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9543: --- Affects Version/s: 2.5.0 2.4.1 > Consumer offset reset after new

[jira] [Commented] (KAFKA-9543) Consumer offset reset after new segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097516#comment-17097516 ] Jason Gustafson commented on KAFKA-9543: I am going to go ahead and close this issue as fixed by

[jira] [Created] (KAFKA-9939) Fetch request metrics are updated twice for delayed fetches

Jason Gustafson created KAFKA-9939: -- Summary: Fetch request metrics are updated twice for delayed fetches Key: KAFKA-9939 URL: https://issues.apache.org/jira/browse/KAFKA-9939 Project: Kafka

[jira] [Updated] (KAFKA-9938) Fix debug consumer read from follower for older protocol versions

[ https://issues.apache.org/jira/browse/KAFKA-9938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9938: --- Affects Version/s: 2.5.0 2.4.1 > Fix debug consumer read from

[jira] [Created] (KAFKA-9938) Fix debug consumer read from follower for older protocol versions

Jason Gustafson created KAFKA-9938: -- Summary: Fix debug consumer read from follower for older protocol versions Key: KAFKA-9938 URL: https://issues.apache.org/jira/browse/KAFKA-9938 Project: Kafka

[jira] [Created] (KAFKA-9927) Add support for varint types to message generator

Jason Gustafson created KAFKA-9927: -- Summary: Add support for varint types to message generator Key: KAFKA-9927 URL: https://issues.apache.org/jira/browse/KAFKA-9927 Project: Kafka Issue

[jira] [Resolved] (KAFKA-9885) Evict last members of a group when the maximum allowed is reached

[ https://issues.apache.org/jira/browse/KAFKA-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9885. Fix Version/s: 2.6.0 Resolution: Fixed > Evict last members of a group when the

[jira] [Updated] (KAFKA-9839) IllegalStateException on metadata update when broker learns about its new epoch after the controller

[ https://issues.apache.org/jira/browse/KAFKA-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9839: --- Affects Version/s: 2.5.0 2.4.1 > IllegalStateException on metadata

[jira] [Resolved] (KAFKA-9839) IllegalStateException on metadata update when broker learns about its new epoch after the controller

[ https://issues.apache.org/jira/browse/KAFKA-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9839. Fix Version/s: 2.5.1 Resolution: Fixed > IllegalStateException on metadata update

[jira] [Resolved] (KAFKA-9844) Maximum number of members within a group is not always enforced due to a race condition in join group

[ https://issues.apache.org/jira/browse/KAFKA-9844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9844. Fix Version/s: 2.6.0 Resolution: Fixed > Maximum number of members within a group

[jira] [Assigned] (KAFKA-9313) Set default for client.dns.lookup to use_all_dns_ips

[ https://issues.apache.org/jira/browse/KAFKA-9313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-9313: -- Assignee: Badai Aqrandista > Set default for client.dns.lookup to use_all_dns_ips >

[jira] [Comment Edited] (KAFKA-9543) Consumer offset reset after new segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085938#comment-17085938 ] Jason Gustafson edited comment on KAFKA-9543 at 4/17/20, 6:19 PM: --

[jira] [Commented] (KAFKA-9543) Consumer offset reset after new segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085938#comment-17085938 ] Jason Gustafson commented on KAFKA-9543: [~junrao] Good suggestion. I opened

[jira] [Created] (KAFKA-9886) Validate segment range before reading in `Log.read`

Jason Gustafson created KAFKA-9886: -- Summary: Validate segment range before reading in `Log.read` Key: KAFKA-9886 URL: https://issues.apache.org/jira/browse/KAFKA-9886 Project: Kafka Issue

[jira] [Commented] (KAFKA-9543) Consumer offset reset after new segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084605#comment-17084605 ] Jason Gustafson commented on KAFKA-9543: In KAFKA-9838, I fixed what I thought was a minor race

[jira] [Resolved] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

[ https://issues.apache.org/jira/browse/KAFKA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9824. Resolution: Duplicate Closing this as a duplicate of KAFKA-9543. Let's continue discussion

[jira] [Resolved] (KAFKA-9838) Add additional log concurrency test cases

[ https://issues.apache.org/jira/browse/KAFKA-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9838. Resolution: Fixed > Add additional log concurrency test cases >

[jira] [Updated] (KAFKA-9838) Add additional log concurrency test cases

[ https://issues.apache.org/jira/browse/KAFKA-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9838: --- Fix Version/s: 2.6.0 > Add additional log concurrency test cases >

[jira] [Updated] (KAFKA-9876) Implement Raft Protocol for Metadata Quorum

[ https://issues.apache.org/jira/browse/KAFKA-9876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9876: --- Description: This tracks the completion of the Raft Protocol specified in KIP-595:

[jira] [Created] (KAFKA-9876) Implement Raft Protocol for Metadata Quorum

Jason Gustafson created KAFKA-9876: -- Summary: Implement Raft Protocol for Metadata Quorum Key: KAFKA-9876 URL: https://issues.apache.org/jira/browse/KAFKA-9876 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-9539) Add leader epoch in StopReplicaRequest

[ https://issues.apache.org/jira/browse/KAFKA-9539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9539. Fix Version/s: 2.6.0 Resolution: Fixed > Add leader epoch in StopReplicaRequest >

[jira] [Resolved] (KAFKA-9842) Address testing gaps in consumer OffsetsForLeaderEpochs request grouping

[ https://issues.apache.org/jira/browse/KAFKA-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9842. Resolution: Fixed > Address testing gaps in consumer OffsetsForLeaderEpochs request

[jira] [Commented] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

[ https://issues.apache.org/jira/browse/KAFKA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082734#comment-17082734 ] Jason Gustafson commented on KAFKA-9824: [~nitay.k] That is what I initially suspected, but now

[jira] [Commented] (KAFKA-9840) Consumer should not use OffsetForLeaderEpoch without current epoch validation

[ https://issues.apache.org/jira/browse/KAFKA-9840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082504#comment-17082504 ] Jason Gustafson commented on KAFKA-9840: Other than the zombie case, the only way I could see

[jira] [Commented] (KAFKA-9840) Consumer should not use OffsetForLeaderEpoch without current epoch validation

[ https://issues.apache.org/jira/browse/KAFKA-9840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082459#comment-17082459 ] Jason Gustafson commented on KAFKA-9840: [~guozhang] If we have the current epoch validation,

[jira] [Resolved] (KAFKA-9583) OffsetsForLeaderEpoch requests are sometimes not sent to the leader of partition

[ https://issues.apache.org/jira/browse/KAFKA-9583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9583. Resolution: Fixed > OffsetsForLeaderEpoch requests are sometimes not sent to the leader of

[jira] [Assigned] (KAFKA-9842) Address testing gaps in consumer OffsetsForLeaderEpochs request grouping

[ https://issues.apache.org/jira/browse/KAFKA-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-9842: -- Assignee: Jason Gustafson > Address testing gaps in consumer OffsetsForLeaderEpochs

[jira] [Created] (KAFKA-9842) Address testing gaps in consumer OffsetsForLeaderEpochs request grouping

Jason Gustafson created KAFKA-9842: -- Summary: Address testing gaps in consumer OffsetsForLeaderEpochs request grouping Key: KAFKA-9842 URL: https://issues.apache.org/jira/browse/KAFKA-9842 Project:

[jira] [Updated] (KAFKA-9840) Consumer should not use OffsetForLeaderEpoch without current epoch validation

[ https://issues.apache.org/jira/browse/KAFKA-9840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9840: --- Description: We have observed a case where the consumer attempted to detect truncation with

[jira] [Updated] (KAFKA-9840) Consumer should not use OffsetForLeaderEpoch without current epoch validation

[ https://issues.apache.org/jira/browse/KAFKA-9840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9840: --- Affects Version/s: 2.4.1 > Consumer should not use OffsetForLeaderEpoch without current

[jira] [Created] (KAFKA-9840) Consumer should not use OffsetForLeaderEpoch without current epoch validation

Jason Gustafson created KAFKA-9840: -- Summary: Consumer should not use OffsetForLeaderEpoch without current epoch validation Key: KAFKA-9840 URL: https://issues.apache.org/jira/browse/KAFKA-9840

[jira] [Commented] (KAFKA-9543) Consumer offset reset after new segment rolling

[ https://issues.apache.org/jira/browse/KAFKA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078829#comment-17078829 ] Jason Gustafson commented on KAFKA-9543: I think this is the same issue as KAFKA-9824. I have

[jira] [Updated] (KAFKA-9835) Race condition with concurrent write allows reads above high watermark

[ https://issues.apache.org/jira/browse/KAFKA-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9835: --- Affects Version/s: (was: 2.4.1) (was: 2.3.1)

[jira] [Created] (KAFKA-9838) Add additional log concurrency test cases

Jason Gustafson created KAFKA-9838: -- Summary: Add additional log concurrency test cases Key: KAFKA-9838 URL: https://issues.apache.org/jira/browse/KAFKA-9838 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-9835) Race condition with concurrent write allows reads above high watermark

[ https://issues.apache.org/jira/browse/KAFKA-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9835: --- Fix Version/s: 2.5.1 2.4.2 > Race condition with concurrent write allows

[jira] [Updated] (KAFKA-9835) Race condition with concurrent write allows reads above high watermark

[ https://issues.apache.org/jira/browse/KAFKA-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9835: --- Affects Version/s: 2.2.2 2.3.1 2.4.1 > Race

[jira] [Resolved] (KAFKA-9835) Race condition with concurrent write allows reads above high watermark

[ https://issues.apache.org/jira/browse/KAFKA-9835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9835. Resolution: Fixed > Race condition with concurrent write allows reads above high watermark

[jira] [Created] (KAFKA-9835) Race condition with concurrent write allows reads above high watermark

Jason Gustafson created KAFKA-9835: -- Summary: Race condition with concurrent write allows reads above high watermark Key: KAFKA-9835 URL: https://issues.apache.org/jira/browse/KAFKA-9835 Project:

[jira] [Commented] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

[ https://issues.apache.org/jira/browse/KAFKA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077521#comment-17077521 ] Jason Gustafson commented on KAFKA-9824: [~nitay.k] Also, it would be helpful to see the full

[jira] [Commented] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

[ https://issues.apache.org/jira/browse/KAFKA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077501#comment-17077501 ] Jason Gustafson commented on KAFKA-9824: [~nitay.k] Thanks for the additional information. I

[jira] [Resolved] (KAFKA-9815) Consumer may never re-join if inconsistent metadata is received once

[ https://issues.apache.org/jira/browse/KAFKA-9815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9815. Fix Version/s: 2.4.2 2.5.0 Resolution: Fixed > Consumer may

[jira] [Commented] (KAFKA-9824) Consumer loses partition offset and resets post 2.4.1 version upgrade

[ https://issues.apache.org/jira/browse/KAFKA-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076516#comment-17076516 ] Jason Gustafson commented on KAFKA-9824: [~nitay.k] Thanks for the report. From the logs, we saw

[jira] [Resolved] (KAFKA-9807) Race condition updating high watermark allows reads above LSO

[ https://issues.apache.org/jira/browse/KAFKA-9807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9807. Fix Version/s: 2.4.2 2.5.0 Resolution: Fixed Resolving this. I

[jira] [Resolved] (KAFKA-9750) Flaky test kafka.server.ReplicaManagerTest.testFencedErrorCausedByBecomeLeader

[ https://issues.apache.org/jira/browse/KAFKA-9750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9750. Resolution: Fixed > Flaky test

[jira] [Updated] (KAFKA-9807) Race condition updating high watermark allows reads above LSO

[ https://issues.apache.org/jira/browse/KAFKA-9807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9807: --- Affects Version/s: 0.11.0.3 1.0.2 1.1.1

[jira] [Created] (KAFKA-9807) Race condition updating high watermark allows reads above LSO

Jason Gustafson created KAFKA-9807: -- Summary: Race condition updating high watermark allows reads above LSO Key: KAFKA-9807 URL: https://issues.apache.org/jira/browse/KAFKA-9807 Project: Kafka

[jira] [Created] (KAFKA-9802) Fix flaky system test `TransactionsTest.test_transactions`

Jason Gustafson created KAFKA-9802: -- Summary: Fix flaky system test `TransactionsTest.test_transactions` Key: KAFKA-9802 URL: https://issues.apache.org/jira/browse/KAFKA-9802 Project: Kafka

[jira] [Updated] (KAFKA-9752) Consumer rebalance can be stuck after new member timeout with old JoinGroup version

[ https://issues.apache.org/jira/browse/KAFKA-9752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9752: --- Description: For older versions of the JoinGroup protocol (v3 and below), there was no way

[jira] [Comment Edited] (KAFKA-9724) Consumer wrongly ignores fetched records "since it no longer has valid position"

[ https://issues.apache.org/jira/browse/KAFKA-9724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071369#comment-17071369 ] Jason Gustafson edited comment on KAFKA-9724 at 3/31/20, 1:12 AM: -- The

[jira] [Commented] (KAFKA-9724) Consumer wrongly ignores fetched records "since it no longer has valid position"

[ https://issues.apache.org/jira/browse/KAFKA-9724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071369#comment-17071369 ] Jason Gustafson commented on KAFKA-9724: The interesting thing in the log snippet is the

[jira] [Resolved] (KAFKA-9600) EndTxn handler should check strict epoch equality

[ https://issues.apache.org/jira/browse/KAFKA-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9600. Fix Version/s: 2.6.0 Resolution: Fixed > EndTxn handler should check strict epoch

[jira] [Created] (KAFKA-9777) Purgatory locking bug can lead to hanging transaction

Jason Gustafson created KAFKA-9777: -- Summary: Purgatory locking bug can lead to hanging transaction Key: KAFKA-9777 URL: https://issues.apache.org/jira/browse/KAFKA-9777 Project: Kafka

[jira] [Updated] (KAFKA-9750) Flaky test kafka.server.ReplicaManagerTest.testFencedErrorCausedByBecomeLeader

[ https://issues.apache.org/jira/browse/KAFKA-9750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9750: --- Fix Version/s: 2.5.0 > Flaky test

[jira] [Updated] (KAFKA-9750) Flaky test kafka.server.ReplicaManagerTest.testFencedErrorCausedByBecomeLeader

[ https://issues.apache.org/jira/browse/KAFKA-9750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9750: --- Priority: Blocker (was: Major) > Flaky test

[jira] [Commented] (KAFKA-9750) Flaky test kafka.server.ReplicaManagerTest.testFencedErrorCausedByBecomeLeader

[ https://issues.apache.org/jira/browse/KAFKA-9750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17067839#comment-17067839 ] Jason Gustafson commented on KAFKA-9750: Elevating this to blocker until we understand the cause.

[jira] [Resolved] (KAFKA-9752) Consumer rebalance can be stuck after new member timeout with old JoinGroup version

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

[jira] [Resolved] (KAFKA-9749) TransactionMarkerRequestCompletionHandler should treat storage exceptions as retriable

[ https://issues.apache.org/jira/browse/KAFKA-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9749. Fix Version/s: 2.4.2 2.3.2 2.5.0 Resolution:

[jira] [Created] (KAFKA-9752) Consumer rebalance can be stuck after new member timeout with old JoinGroup version

Jason Gustafson created KAFKA-9752: -- Summary: Consumer rebalance can be stuck after new member timeout with old JoinGroup version Key: KAFKA-9752 URL: https://issues.apache.org/jira/browse/KAFKA-9752

[jira] [Resolved] (KAFKA-9654) ReplicaAlterLogDirsThread can't be created again if the previous ReplicaAlterLogDirsThreadmeet encounters leader epoch error

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

[jira] [Updated] (KAFKA-9658) Removing default user quota doesn't take effect until broker restart

[ https://issues.apache.org/jira/browse/KAFKA-9658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9658: --- Fix Version/s: (was: 2.5.1) 2.5.0 > Removing default user quota

[jira] [Created] (KAFKA-9737) Describing log dir reassignment times out if broker is offline

Jason Gustafson created KAFKA-9737: -- Summary: Describing log dir reassignment times out if broker is offline Key: KAFKA-9737 URL: https://issues.apache.org/jira/browse/KAFKA-9737 Project: Kafka

[jira] [Commented] (KAFKA-9724) Consumer wrongly ignores fetched records "since it no longer has valid position"

[ https://issues.apache.org/jira/browse/KAFKA-9724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062787#comment-17062787 ] Jason Gustafson commented on KAFKA-9724: [~o.muravskiy] Thanks for the report. Could you include

[jira] [Resolved] (KAFKA-9656) TxnOffsetCommit should not return COORDINATOR_LOADING error for old request versions

[ https://issues.apache.org/jira/browse/KAFKA-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9656. Fix Version/s: 2.6.0 Resolution: Fixed > TxnOffsetCommit should not return

[jira] [Resolved] (KAFKA-8001) AlterLogDirs: Fetch from future replica stalls when local replica becomes a leader

[ https://issues.apache.org/jira/browse/KAFKA-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8001. Resolution: Duplicate This issue is being addressed in the patch for KAFKA-9654, so I will

[jira] [Resolved] (KAFKA-9670) Benchmark and optimize MetadataResponse preparation

[ https://issues.apache.org/jira/browse/KAFKA-9670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9670. Resolution: Fixed > Benchmark and optimize MetadataResponse preparation >

[jira] [Resolved] (KAFKA-9715) TransactionStateManager: Eliminate unused reference to interBrokerProtocolVersion

[ https://issues.apache.org/jira/browse/KAFKA-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9715. Resolution: Fixed > TransactionStateManager: Eliminate unused reference to >

[jira] [Commented] (KAFKA-9144) Early expiration of producer state can cause coordinator epoch to regress

[ https://issues.apache.org/jira/browse/KAFKA-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058443#comment-17058443 ] Jason Gustafson commented on KAFKA-9144: We found that this bug can also result in a hanging

[jira] [Resolved] (KAFKA-9605) EOS Producer could throw illegal state if trying to complete a failed batch after fatal error

[ https://issues.apache.org/jira/browse/KAFKA-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9605. Resolution: Fixed > EOS Producer could throw illegal state if trying to complete a failed

[jira] [Resolved] (KAFKA-9658) Removing default user quota doesn't take effect until broker restart

[ https://issues.apache.org/jira/browse/KAFKA-9658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9658. Fix Version/s: 2.4.2 2.3.2 2.5.1 Resolution:

[jira] [Commented] (KAFKA-9682) Flaky Test KafkaBasedLogTest#testSendAndReadToEnd

[ https://issues.apache.org/jira/browse/KAFKA-9682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054275#comment-17054275 ] Jason Gustafson commented on KAFKA-9682: This fails 100% of the time locally for me. cc [~rhauch]

[jira] [Assigned] (KAFKA-9678) Introduce bounded exponential backoff in clients

[ https://issues.apache.org/jira/browse/KAFKA-9678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-9678: -- Assignee: Sanjana Kaundinya > Introduce bounded exponential backoff in clients >

[jira] [Commented] (KAFKA-9666) Transactional producer Epoch could not be reset

[ https://issues.apache.org/jira/browse/KAFKA-9666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053596#comment-17053596 ] Jason Gustafson commented on KAFKA-9666: This seems not to be a regression. This was encountered

[jira] [Updated] (KAFKA-9666) Transactional producer Epoch could not be reset

[ https://issues.apache.org/jira/browse/KAFKA-9666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9666: --- Priority: Critical (was: Blocker) > Transactional producer Epoch could not be reset >

[jira] [Updated] (KAFKA-9666) Transactional producer Epoch could not be reset

[ https://issues.apache.org/jira/browse/KAFKA-9666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9666: --- Fix Version/s: 2.5.0 > Transactional producer Epoch could not be reset >

[jira] [Commented] (KAFKA-9666) Transactional producer Epoch could not be reset

[ https://issues.apache.org/jira/browse/KAFKA-9666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052342#comment-17052342 ] Jason Gustafson commented on KAFKA-9666: cc [~mumrah] We may need this for 2.5. I am not sure if

[jira] [Updated] (KAFKA-9666) Transactional producer Epoch could not be reset

[ https://issues.apache.org/jira/browse/KAFKA-9666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9666: --- Priority: Blocker (was: Major) > Transactional producer Epoch could not be reset >

[jira] [Updated] (KAFKA-9656) TxnOffsetCommit should not return COORDINATOR_LOADING error for old request versions

[ https://issues.apache.org/jira/browse/KAFKA-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9656: --- Description: In KAFKA-7296, we fixed a bug which causes the producer to enter a fatal state

[jira] [Created] (KAFKA-9656) TxnOffsetCommit should not return COORDINATOR_LOADING error for old request versions

Jason Gustafson created KAFKA-9656: -- Summary: TxnOffsetCommit should not return COORDINATOR_LOADING error for old request versions Key: KAFKA-9656 URL: https://issues.apache.org/jira/browse/KAFKA-9656

[jira] [Created] (KAFKA-9652) Throttle time metric needs to be updated for KIP-219

Jason Gustafson created KAFKA-9652: -- Summary: Throttle time metric needs to be updated for KIP-219 Key: KAFKA-9652 URL: https://issues.apache.org/jira/browse/KAFKA-9652 Project: Kafka Issue

[jira] [Assigned] (KAFKA-8001) AlterLogDirs: Fetch from future replica stalls when local replica becomes a leader

[ https://issues.apache.org/jira/browse/KAFKA-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-8001: -- Assignee: Jason Gustafson (was: Vikas Singh) > AlterLogDirs: Fetch from future

[jira] [Updated] (KAFKA-9600) EndTxn handler should check strict epoch equality

[ https://issues.apache.org/jira/browse/KAFKA-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9600: --- Description: The EndTxn path in TransactionCoordinator is shared between direct calls to

[jira] [Created] (KAFKA-9600) EndTxn handler should check strict epoch equality

Jason Gustafson created KAFKA-9600: -- Summary: EndTxn handler should check strict epoch equality Key: KAFKA-9600 URL: https://issues.apache.org/jira/browse/KAFKA-9600 Project: Kafka Issue

[jira] [Resolved] (KAFKA-9541) Flaky Test DescribeConsumerGroupTest#testDescribeGroupMembersWithShortInitializationTimeout

[ https://issues.apache.org/jira/browse/KAFKA-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9541. Resolution: Fixed > Flaky Test >

[jira] [Commented] (KAFKA-9541) Flaky Test DescribeConsumerGroupTest#testDescribeGroupMembersWithShortInitializationTimeout

[ https://issues.apache.org/jira/browse/KAFKA-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17043019#comment-17043019 ] Jason Gustafson commented on KAFKA-9541: This is fixed by KAFKA-9530. > Flaky Test >

[jira] [Resolved] (KAFKA-9530) Flaky Test kafka.admin.DescribeConsumerGroupTest.testDescribeGroupWithShortInitializationTimeout

[ https://issues.apache.org/jira/browse/KAFKA-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9530. Resolution: Fixed > Flaky Test >

[jira] [Created] (KAFKA-9596) Hanging test case `testMaxLogCompactionLag`

Jason Gustafson created KAFKA-9596: -- Summary: Hanging test case `testMaxLogCompactionLag` Key: KAFKA-9596 URL: https://issues.apache.org/jira/browse/KAFKA-9596 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-9577) Client encountering SASL_HANDSHAKE protocol version errors on 2.5 / trunk

[ https://issues.apache.org/jira/browse/KAFKA-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9577. Resolution: Fixed > Client encountering SASL_HANDSHAKE protocol version errors on 2.5 /

[jira] [Commented] (KAFKA-9593) Kafka config allows updating a nonexistent config and makes it mandatory to specify the config for further config updates

[ https://issues.apache.org/jira/browse/KAFKA-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042234#comment-17042234 ] Jason Gustafson commented on KAFKA-9593: The message could be improved here, but I think the main

[jira] [Created] (KAFKA-9595) Config tool should use admin client's incremental config API

Jason Gustafson created KAFKA-9595: -- Summary: Config tool should use admin client's incremental config API Key: KAFKA-9595 URL: https://issues.apache.org/jira/browse/KAFKA-9595 Project: Kafka

[jira] [Resolved] (KAFKA-9206) Consumer should handle `CORRUPT_MESSAGE` error code in fetch response

[ https://issues.apache.org/jira/browse/KAFKA-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9206. Fix Version/s: 2.6.0 Resolution: Fixed > Consumer should handle `CORRUPT_MESSAGE`

[jira] [Assigned] (KAFKA-9577) Client encountering SASL_HANDSHAKE protocol version errors on 2.5 / trunk

[ https://issues.apache.org/jira/browse/KAFKA-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-9577: -- Assignee: Lucas Bradstreet > Client encountering SASL_HANDSHAKE protocol version

[jira] [Resolved] (KAFKA-9544) Flaky Test `KafkaAdminClientTest.testDefaultApiTimeoutOverride`

[ https://issues.apache.org/jira/browse/KAFKA-9544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9544. Resolution: Fixed > Flaky Test `KafkaAdminClientTest.testDefaultApiTimeoutOverride` >

[jira] [Updated] (KAFKA-9558) getListOffsetsCalls doesn't update node in case of leader change

[ https://issues.apache.org/jira/browse/KAFKA-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-9558: --- Affects Version/s: (was: 2.5.0) > getListOffsetsCalls doesn't update node in case of

[jira] [Resolved] (KAFKA-9535) Metadata not updated when consumer encounters FENCED_LEADER_EPOCH

[ https://issues.apache.org/jira/browse/KAFKA-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9535. Fix Version/s: 2.4.1 2.3.2 2.5.0 Resolution:

[jira] [Resolved] (KAFKA-8805) Bump producer epoch following recoverable errors

[ https://issues.apache.org/jira/browse/KAFKA-8805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8805. Fix Version/s: 2.5.0 Resolution: Fixed > Bump producer epoch following recoverable

[jira] [Updated] (KAFKA-8507) Support --bootstrap-server in all command line tools

[ https://issues.apache.org/jira/browse/KAFKA-8507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-8507: --- Affects Version/s: (was: 2.5.0) > Support --bootstrap-server in all command line tools >

<    3   4   5   6   7   8   9   10   11   12   >