[jira] [Resolved] (KAFKA-10619) Producer will enable EOS by default

[ https://issues.apache.org/jira/browse/KAFKA-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantine Karantasis resolved KAFKA-10619. Resolution: Fixed The [PR|https://github.com/apache/kafka/pull/9497] has

[jira] [Resolved] (KAFKA-6987) Reimplement KafkaFuture with CompletableFuture

[ https://issues.apache.org/jira/browse/KAFKA-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantine Karantasis resolved KAFKA-6987. --- Resolution: Fixed > Reimplement KafkaFuture with CompletableFuture >

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #299

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.0 #7

See

[jira] [Created] (KAFKA-13046) Improve the test coverage for stickyAssignor

Luke Chen created KAFKA-13046: - Summary: Improve the test coverage for stickyAssignor Key: KAFKA-13046 URL: https://issues.apache.org/jira/browse/KAFKA-13046 Project: Kafka Issue Type: Test

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #298

See Changes: -- [...truncated 480479 lines...] [2021-07-08T00:55:55.749Z] [2021-07-08T00:55:55.749Z] KafkaMetricReporterExceptionHandlingTest >

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.0 #6

See

[jira] [Created] (KAFKA-13045) Add test for batched OffsetFetch requests where we have the same group in the request twice.

Sanjana Kaundinya created KAFKA-13045: - Summary: Add test for batched OffsetFetch requests where we have the same group in the request twice. Key: KAFKA-13045 URL:

[jira] [Resolved] (KAFKA-10580) Add topic ID support to Fetch request

[ https://issues.apache.org/jira/browse/KAFKA-10580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10580. - Fix Version/s: 3.1.0 Resolution: Fixed merged the PR to trunk. > Add topic ID support to Fetch

Re: [DISCUSS] KIP-760: Increase minimum value of segment.ms and segment.bytes

Ryanne/James Yes, the proposed values are kinda arbitrary. I just want to prevent users from setting segment.ms to 1 ms or segment.bytes to 1 byte, which will blow the file handles count and crash the broker. Because of that and James' input, I have updated the KIP to add broker configuration to

[jira] [Resolved] (KAFKA-7458) Avoid enforced processing during bootstrap phase

[ https://issues.apache.org/jira/browse/KAFKA-7458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-7458. - Resolution: Fixed > Avoid enforced processing during bootstrap phase >

[jira] [Resolved] (KAFKA-8410) Strengthen the types of Processors, at least in the DSL, maybe in the PAPI as well

[ https://issues.apache.org/jira/browse/KAFKA-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-8410. - Resolution: Fixed > Strengthen the types of Processors, at least in the DSL, maybe in the PAPI

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #297

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.0 #5

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.0 #4

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #296

See

Re: [DISCUSS] KIP-501 Avoid out-of-sync or offline partitions when follower fetch requests are not processed in time

Hi, Satish, Thanks for the KIP. 1. For Solution 2, we probably want to be a bit careful with letting each broker automatically relinquish leadership. The danger of doing that is if all brokers start doing the same (say due to increased data volume), the whole cluster could get into a state with

Re: [DISCUSS] KIP-760: Increase minimum value of segment.ms and segment.bytes

Badai, the KIP makes sense to me, but could you maybe add some evidence to support your proposed values? I'm sure they come from experience but I don't think they are obvious and so may appear arbitrary. Ryanne On Tue, Jul 6, 2021, 4:23 PM Badai Aqrandista wrote: > Hi all > > I have just

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #295

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.0 #3

See

[jira] [Created] (KAFKA-13044) __consumer_offsets corruption

Nanda Kishore M S created KAFKA-13044: - Summary: __consumer_offsets corruption Key: KAFKA-13044 URL: https://issues.apache.org/jira/browse/KAFKA-13044 Project: Kafka Issue Type: Bug

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #294

See

[jira] [Created] (KAFKA-13043) Add Admin API for batched offset fetch requests (KIP-709)

Rajini Sivaram created KAFKA-13043: -- Summary: Add Admin API for batched offset fetch requests (KIP-709) Key: KAFKA-13043 URL: https://issues.apache.org/jira/browse/KAFKA-13043 Project: Kafka

[jira] [Resolved] (KAFKA-12234) Extend OffsetFetch requests to accept multiple group ids.

[ https://issues.apache.org/jira/browse/KAFKA-12234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-12234. Reviewer: Rajini Sivaram Resolution: Fixed > Extend OffsetFetch requests to accept

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #293

See Changes: -- [...truncated 478275 lines...] [2021-07-07T09:21:59.636Z] ControllerIntegrationTest > testPartitionReassignmentToBrokerWithOfflineLogDir() STARTED

[jira] [Resolved] (KAFKA-13000) Improve handling of UnsupportedVersionException in MockClient

[ https://issues.apache.org/jira/browse/KAFKA-13000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-13000. Fix Version/s: 3.0.0 Assignee: (was: Kirk True) Resolution: Fixed >

[jira] [Resolved] (KAFKA-13029) FindCoordinators batching can break consumers during rolling upgrade

[ https://issues.apache.org/jira/browse/KAFKA-13029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-13029. Resolution: Fixed > FindCoordinators batching can break consumers during rolling upgrade

Re: [DISCUSS] KIP-729 Custom validation of records on the broker prior to log append

Hello, James. > One use case we would like is to require that producers are sending > compressed messages. I think that forcing producers to send compressed messages is out of scope of this KIP. > 7 июля 2021 г., в 08:48, Soumyajit Sahu написал(а): > > Interesting point. You are correct

[jira] [Created] (KAFKA-13042) Flaky test KafkaMetadataLogTest.testDeleteSnapshots()

dengziming created KAFKA-13042: -- Summary: Flaky test KafkaMetadataLogTest.testDeleteSnapshots() Key: KAFKA-13042 URL: https://issues.apache.org/jira/browse/KAFKA-13042 Project: Kafka Issue

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #292

See

Re: [DISCUSS] KIP-760: Increase minimum value of segment.ms and segment.bytes

James Thank you for replying. I originally thought about adding two new broker dynamic config to allow administrator to determine the acceptable minimum: min.topic.segment.ms min.topic.segment.bytes I put this in the "rejected alternatives" section because I think adding two more configs to the