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

See

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

See Changes: -- [...truncated 531516 lines...] [Pipeline] echo [2023-02-11T01:43:20.736Z] Skipping Kafka Streams archetype test for Java 11 [Pipeline] } [Pipeline] // withE

Re: [VOTE] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

+1 (non-binding). Le ven. 10 févr. 2023 à 19:02, Calvin Liu a écrit : > > Hi all, > > I'd like to call for a vote on KIP-903, which proposes a fix to the broker > reboot data loss KAFKA-14139 > > It changes the Fetch and AlterPartition requests

[VOTE] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

Hi all, I'd like to call for a vote on KIP-903, which proposes a fix to the broker reboot data loss KAFKA-14139 It changes the Fetch and AlterPartition requests to include the broker epochs. Then the controller can use these epochs to help reject

Re: [DISCUSS] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

Hi David, 01. It is a good idea to fence some delayed Fetch requests from the reboot followers. 06. Ack 09. Rephrased the sentence to let the ZK controller ignore the broker epoch. Thanks, Calvin. On Fri, Feb 10, 2023 at 6:11 AM David Jacot wrote: > Hi Calvin, > > 01. Yeah, this should generall

[jira] [Resolved] (KAFKA-14688) Move org.apache.kafka.server.log.internals to org.apache.kafka.storage.internals.log

[ https://issues.apache.org/jira/browse/KAFKA-14688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-14688. - Resolution: Fixed > Move org.apache.kafka.server.log.internals to > org.apache.kafka.storage.in

Re: [DISCUSS] KIP-905: Broker interceptors

Hi Ahmed, Thanks for taking a look at the KIP, and for your insightful feedback! I don't disagree with the sentiment that in-band interceptors could be a potential source of bugs in a cluster. Having said that, I don't necessarily think that an in-band interceptor is significantly riskier than a

[GitHub] [kafka-site] C0urante opened a new pull request, #491: MINOR: Fix anchor links in Connect docs

C0urante opened a new pull request, #491: URL: https://github.com/apache/kafka-site/pull/491 Missing `#` at the beginning of links leads to 404s when users click on them. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

Contribute

hey, I'd like to contribute to kafka

Re: [DISCUSS] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

Hi Calvin, 01. Yeah, this should generally not happen. I was wondering if it could happen in the case of a partial failure of a broker for instance. Generally, I think that being defensive on the leader side does not hurt here. I am perhaps too extreme here. 03. NewIsr does not need to be ignorab

Re: [DISCUSS] KIP-905: Broker interceptors

Hi David, That's a very interesting KIP and I wanted to share my two cents. I believe there's a lot of value and use cases for the ability to intercept, mutate and filter Kafka's messages, however I'm not sure if trying to achieve that via in-band interceptors is the best approach for this. -

[jira] [Created] (KAFKA-14705) Delete kafka.tools.JmxTool redirection object

Federico Valeri created KAFKA-14705: --- Summary: Delete kafka.tools.JmxTool redirection object Key: KAFKA-14705 URL: https://issues.apache.org/jira/browse/KAFKA-14705 Project: Kafka Issue Typ

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

See