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

See

Re: [DISCUSS] KIP-926: introducing acks=min.insync.replicas config

Hi Luke, It's a good point that add this config and get better P99 latency, but is this changing the meaning of "in sync replicas"? consider a situation with "replica=3 acks=2", when two broker fail and left only the broker that does't have the message, it is in sync, so will be elected as

Re: [VOTE] KIP-872: Add Serializer#serializeToByteBuffer() to reduce memory copying

+1(binding) from me. Thanks for the improvement! Luke On Sun, May 7, 2023 at 6:34 PM Divij Vaidya wrote: > Vote +1 (non binding) > > I think that this is a nice improvement as it prevents an unnecessary data > copy for users who are using ByteBuffer serialization on the producer. > > -- >

Re: [DISCUSS] KIP-927: Improve the kafka-metadata-quorum output

Hi Fede, Thanks for the KIP. LGTM. @Divij I think the timestamp is timezone independent, so it should be fine. Luke On Thu, May 11, 2023 at 2:04 AM Divij Vaidya wrote: > Thank you for the KIP. > > The current proposal has the limitation that it uses a duration syntax for > representation of

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

See

Re: [VOTE] KIP-864: Add End-To-End Latency Metrics to Connectors

Hi everyone, Bumping this vote thread. 2 +1 binding and 1 +1 non-binding so far. Cheers, Jorge. On Mon, 27 Feb 2023 at 18:56, Knowles Atchison Jr wrote: > +1 (non binding) > > On Mon, Feb 27, 2023 at 11:21 AM Chris Egerton > wrote: > > > Hi all, > > > > I could have sworn I +1'd this but I

Re: [DISCUSS] Apache Kafka 3.5.0 release

Thanks Mickael -- the fix has been merged to 3.5 now On Wed, May 10, 2023 at 1:12 AM Mickael Maison wrote: > Hi Sophie, > > Yes that's fine, thanks for letting me know! > > Mickael > > On Tue, May 9, 2023 at 10:54 PM Sophie Blee-Goldman > wrote: > > > > Hey Mickael, I noticed a bug in the new

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

See Changes: -- [...truncated 472274 lines...] [2023-05-10T18:33:27.694Z] [2023-05-10T18:33:27.694Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 178

Re: [DISCUSS] KIP-927: Improve the kafka-metadata-quorum output

Thank you for the KIP. The current proposal has the limitation that it uses a duration syntax for representation of a timestamp. Also, the syntax relies on the locale and timezone of the caller machine. This makes it difficult to share the output with others. As an example, let's say you want to

Re: [DISCUSS] KIP-926: introducing acks=min.insync.replicas config

Hi, Luke, Thanks for the KIP. It clearly highlights the tradeoff between latency and durability and proposes an approach relaxing a durability constraint to provide lower ingestion latency. Please find a few comments/questions. 100. The KIP makes one statement which may be considered critical:

[jira] [Resolved] (KAFKA-14985) ConnectionQuotasTest.testListenerConnectionRateLimitWhenActualRateAboveLimit() test is flaky

[ https://issues.apache.org/jira/browse/KAFKA-14985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divij Vaidya resolved KAFKA-14985. -- Resolution: Duplicate Resolving as duplicate of existing open JIRA. >

Re: apply for permission to contribute to Apache Kafka

I just checked permissions and you should be all set. Did you try to log out and log in again? -Matthias On 5/9/23 10:04 PM, Doe John wrote: Thanks, After obtaining permission, I want to assign this JIRA ticket

Re: Question ❓

Partitions are not for different users. If you want to isolate users, you would do it at the topic level. You could use ACLs to grant access to different topics: https://kafka.apache.org/documentation/#security_authz -Matthias On 5/9/23 11:11 AM, влад тасканов wrote: Hi. I recently

[DISCUSS] KIP-927: Improve the kafka-metadata-quorum output

Hi all, I'd like to start a new discussion thread on KIP-927: Improve the kafka-metadata-quorum output. https://cwiki.apache.org/confluence/display/KAFKA/KIP-927%3A+Improve+the+kafka-metadata-quorum+output This KIP is small and proposes to add a new optional flag to have a human-readable

[jira] [Created] (KAFKA-14985) ConnectionQuotasTest.testListenerConnectionRateLimitWhenActualRateAboveLimit() test is flaky

Manyanda Chitimbo created KAFKA-14985: - Summary: ConnectionQuotasTest.testListenerConnectionRateLimitWhenActualRateAboveLimit() test is flaky Key: KAFKA-14985 URL:

[jira] [Created] (KAFKA-14984) DynamicBrokerReconfigurationTest.testThreadPoolResize() test is flaky

Manyanda Chitimbo created KAFKA-14984: - Summary: DynamicBrokerReconfigurationTest.testThreadPoolResize() test is flaky Key: KAFKA-14984 URL: https://issues.apache.org/jira/browse/KAFKA-14984

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

See Changes: -- [...truncated 567823 lines...] [2023-05-10T15:11:29.020Z] [2023-05-10T15:11:29.020Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 180

Re: [DISCUSS] KIP-926: introducing acks=min.insync.replicas config

Thank you Luke for starting off this discussion. I have been thinking about this and other similar changes to the replication for a while now. The KIP that Ismael surfaced (where was that discussion thread hiding all this time!) addresses exactly the improvements that I have been wondering about.

[jira] [Created] (KAFKA-14983) Upgrade jetty-server to 9.4.51

Beltran created KAFKA-14983: --- Summary: Upgrade jetty-server to 9.4.51 Key: KAFKA-14983 URL: https://issues.apache.org/jira/browse/KAFKA-14983 Project: Kafka Issue Type: Task Reporter:

[jira] [Resolved] (KAFKA-14514) Implement range broker side assignor

[ https://issues.apache.org/jira/browse/KAFKA-14514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-14514. - Fix Version/s: 3.6.0 Resolution: Fixed > Implement range broker side assignor >

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

See Changes: -- [...truncated 472431 lines...] [2023-05-10T11:26:08.957Z] > Task :connect:json:testClasses UP-TO-DATE [2023-05-10T11:26:08.957Z] > Task

Re: Question ❓

The current request queue is very single. In fact, there will be many performance problems when the business scenario of a single cluster becomes complicated. Not only to divide according to user, but also to isolate according to request category, this is just my idea. best, hudeqi

[jira] [Created] (KAFKA-14982) Improve the kafka-metadata-quorum output

Luke Chen created KAFKA-14982: - Summary: Improve the kafka-metadata-quorum output Key: KAFKA-14982 URL: https://issues.apache.org/jira/browse/KAFKA-14982 Project: Kafka Issue Type: Improvement

Question ❓

Hi. I recently start­ed studying kafka and raised a question. Is it possible for each user to make a separate queue? as I understand it, there is a broker with different topics, and each topic had the number of partitions = the number of use­rs. if yes, you can link to an example or

Re: [DISCUSS] Apache Kafka 3.5.0 release

Hi Sophie, Yes that's fine, thanks for letting me know! Mickael On Tue, May 9, 2023 at 10:54 PM Sophie Blee-Goldman wrote: > > Hey Mickael, I noticed a bug in the new versioned key-value byte store > where it's delegating to the wrong API > (copy/paste error I assume). I extracted this into