Clarification Kafka

Dear Team, We wanted to use kafka and therefore installed on ubuntu ( Ubuntu 20.04.4 LTS ) kafka ( 3.2.0  & zoopkeeper 3.6.3--6401e4ad2087061bc6b9f80dec2d69f2e3c8660a) . With this installation, we wanted to connect to mysql server installed on the same  server. Is it possible? If so what

Re: [VOTE] KIP-847

Hello, There was an additional discussion and the KIP got changed as a result of that. I would like to restart the vote on the updated https://cwiki.apache.org/confluence/display/KAFKA/KIP-847%3A+Add+ProducerIdCount+metrics . -Artem On Fri, Jun 24, 2022 at 7:49 PM Luke Chen wrote: > Hi Artem,

[jira] [Reopened] (KAFKA-13152) Replace "buffered.records.per.partition" with "input.buffer.max.bytes"

[ https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reopened KAFKA-13152: - > Replace "buffered.records.per.partition" with "input.buffer.max.bytes" >

Re: [DISCUSS] KIP-837 Allow MultiCasting a Result Record.

Thanks for explaining you reasoning. I agree that it might not be ideal to have both methods implemented, but if we deprecate the exiting one, it would only be an issue until we remove the old one? Or do we see value to keep both methods? In general, working with interfaces is cleaner than wi

[jira] [Resolved] (KAFKA-14050) Older clients cannot deserialize ApiVersions response with finalized feature epoch

[ https://issues.apache.org/jira/browse/KAFKA-14050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-14050. - Resolution: Not A Problem I'm going to close this since the incompatible schema change d

Re: [DISCUSS] KIP-842: Add richer group offset reset mechanisms

I am not sure if we can/should change the behavior of existing "latest/earliest" due to backward compatibility concerns. While I agree that many users might not know the fine details how both behave, it would still be a change that might break other people that do understand the details and rel

[jira] [Created] (KAFKA-14055) Transaction markers may be lost during cleaning if data keys conflict with marker keys

Jason Gustafson created KAFKA-14055: --- Summary: Transaction markers may be lost during cleaning if data keys conflict with marker keys Key: KAFKA-14055 URL: https://issues.apache.org/jira/browse/KAFKA-14055

Re: virtual KIP meeting for KIP-405

Hi, Divij, We stopped doing regular virtual meetings. The progress could be tracked at https://issues.apache.org/jira/browse/KAFKA-7739. Thanks, Jun On Thu, Jul 7, 2022 at 3:41 AM Divij Vaidya wrote: > Hello > > Are we still having a regular virtual meeting to discuss the progress and > out

[jira] [Created] (KAFKA-14054) Unexpected client shutdown as TimeoutException is thrown as IllegalStateException

Donald created KAFKA-14054: -- Summary: Unexpected client shutdown as TimeoutException is thrown as IllegalStateException Key: KAFKA-14054 URL: https://issues.apache.org/jira/browse/KAFKA-14054 Project: Kafka

Re: [DISCUSS] Apache Kafka 3.3.0 Release

On Thu, Jul 7, 2022 at 7:20 AM Sagar wrote: > Pr for KIP-843 also got merged almost 24 days ago. There’s a follow up pr > open for documentation changes. Could this also be added plz? Thank you. Added KIP-843 to the list of KIPs for 3.3.0. I will create a release branch for 3.3 next Monday, 11th

Re: [DISCUSS] Apache Kafka 3.3.0 Release

Hi Jose, Pr for KIP-843 also got merged almost 24 days ago. There’s a follow up pr open for documentation changes. Could this also be added plz? Sagar. On Thu, 7 Jul 2022 at 7:44 PM, José Armando García Sancio wrote: > Hi all, > > Friendly reminder that Feature Freeze was yesterday July 6th. T

Re: [DISCUSS] Apache Kafka 3.3.0 Release

Hi all, Friendly reminder that Feature Freeze was yesterday July 6th. The Code Freeze date is the 20th of July. On Wed, Jun 22, 2022 at 7:45 AM Viktor Somogyi-Vass wrote: > KIP-373 just went in yesterday (and likely add some docs too today), would > you please add it to the list? I added KIP-37

Re: virtual KIP meeting for KIP-405

Hello Are we still having a regular virtual meeting to discuss the progress and outstanding issues? If yes, can you please add me to it (email address: divijvaidy...@gmail.com). Thank you. On 2020/08/20 22:19:57 Jun Rao wrote: > Hi, everyone, > > We plan to have weekly virtual meetings for KI

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

See Changes: -- [...truncated 568148 lines...] [2022-07-07T10:07:31.448Z] /home/jenkins/jenkins-agent/workspace/Kafka_kafka_trunk/streams/src/main/java/org/apache/kafka/st

Re: [Vote] KIP-787 - MM2 Interface to manage Kafka resources

Close the voting with 3 +1 binding and +1 non-binding. Thanks, everyone On Wed, Jul 6, 2022 at 8:16 PM David Jacot wrote: > Thanks for the KIP, Omnia! +1 (binding) > > On Wed, Jul 6, 2022 at 5:02 PM Omnia Ibrahim > wrote: > > > > Hi, > > Can we have one last binding vote for this KIP, please?

Re: Transactions, delivery timeout and changing transactional producer behavior

Thanks for the feedback, I created https://issues.apache.org/jira/browse/KAFKA-14053 and started working on a PR. Luke, for the workaround, we used the transaction admin tool released in 3.0 to "abort" these hanging batches manually. Naturally, the cluster health should be stabilized. This issue p

[jira] [Created] (KAFKA-14053) Transactional producer should bump the epoch when a batch encounters delivery timeout

Daniel Urban created KAFKA-14053: Summary: Transactional producer should bump the epoch when a batch encounters delivery timeout Key: KAFKA-14053 URL: https://issues.apache.org/jira/browse/KAFKA-14053