Re: [DISCUSS] Apache Kafka 3.1.1

Thank you, Tom! +1 Best, Bruno On 09.03.22 19:55, David Jacot wrote: +1. Thanks Tom! Le mer. 9 mars 2022 à 19:10, Bill Bejeck a écrit : Thanks Tom! It's a +1 for me. -Bill On Wed, Mar 9, 2022 at 12:00 PM Ismael Juma wrote: Thanks Tom. +1 Ismael On Wed, Mar 9, 2022 at 8:10 AM Tom B

Re: [DISCUSS] Apache Kafka 3.1.1

I think I was supposed to publish the release plan at the same time as calling the vote for the release. Here it is: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.1.1 Kind regards, Tom On Thu, 10 Mar 2022 at 08:49, Bruno Cadonna wrote: > Thank you, Tom! > > +1 > > Best, > Br

[DISCUSS] Support of ARM and PowerPC

Hi, We recently added ARM (aarch64) and PowerPC (ppc64le) support to the Apache Kafka CI. So now all builds are tested (and work!) on x86_64, aarch64 and ppc64le. Thanks again to the community members that donated the machines. Since we test these platforms, should we consider them as officially

Re: [DISCUSS] Apache Kafka 3.1.1

+1 Thanks Tom for volunteering! On Thu, Mar 10, 2022 at 10:34 AM Tom Bentley wrote: > > I think I was supposed to publish the release plan at the same time as > calling the vote for the release. > Here it is: > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.1.1 > > Kind regards,

Re: [VOTE] 3.0.1 RC0

Hi Mickael, - Executed kafka-verify-rc with no issues - Used the staged Scala 2.13 binaries to run a MM2 DR scenario - Used staging Maven repository with my own test Java clients +1 (non-binding) Thanks Fede On Wed, Mar 9, 2022 at 6:01 PM Bill Bejeck wrote: > > Hi Mickael, > > Thanks for run

New contributor

Hello, could you add me to the contributor list? Jira/Wiki user: fvaleri Br Fede

Re: [VOTE] 3.0.1 RC0

Hi, David, Bill: Yes I haven't updated the website yet. I'll do that next. Thanks everyone for checking the release, I'll close the vote and send the results On Thu, Mar 10, 2022 at 5:29 PM Federico Valeri wrote: > > Hi Mickael, > > - Executed kafka-verify-rc with no issues > - Used the staged

Re: New contributor

Hi Federico, I've added you to the contributor list on JIRA but I couldn't find your user in Confluence. Can you verify the username of your Confluence account? Thanks, Mickael On Thu, Mar 10, 2022 at 5:29 PM Federico Valeri wrote: > > Hello, could you add me to the contributor list? > > Jira

Re: New contributor

Thanks Mickael, now you should have the Confluence account with the same username (fvaleri). On Thu, Mar 10, 2022 at 6:23 PM Mickael Maison wrote: > > Hi Federico, > > I've added you to the contributor list on JIRA but I couldn't find > your user in Confluence. Can you verify the username of your

Re: New contributor

I've added you to the wiki. Thanks for your interest in Apache Kafka! On Thu, Mar 10, 2022 at 6:42 PM Federico Valeri wrote: > > Thanks Mickael, now you should have the Confluence account with the > same username (fvaleri). > > On Thu, Mar 10, 2022 at 6:23 PM Mickael Maison > wrote: > > > > Hi

[RESULTS] [VOTE] Release Kafka version 3.0.1

This vote passes with 7 +1 votes (3 bindings) and no 0 or -1 votes. +1 votes PMC Members: * Tom Bentley * David Jacot * Bill Bejeck Committers: * Luke Chen Community: * Jakub Scholz * Michal Tóth * Federico Valeri 0 votes * No votes -1 votes * No votes Vote thread: https://lists.apache.org/th

Re: [DISCUSS] KIP-714: Client metrics and observability

Jun, >> 28. For the broker metrics, could you spell out the full metric name >> including groups, tags, etc? We typically don't add the broker_id label for >> broker metrics. Also, brokers use Yammer metrics, which doesn't have type >> Sum. Sure, I will update the KIP-714 with t

Re: [DISCUSS] KIP-794: Strictly Uniform Sticky Partitioner

Hi, Artem, Thanks for the updated KIP. A couple of more comments. 30. For the 3 new configs, it would be useful to make it clear that they are only relevant when the partitioner class is null. 31. partitioner.adaptive.partitioning.enable : I am wondering whether it should default to true. This i

Re: [DISCUSS] KIP-714: Client metrics and observability

Hi, Kirk, Sarat, Thanks for the reply. 28. On the broker, we typically use Yammer metrics. Only for metrics that depend on Kafka metric features (e.g., quota), we use the Kafka metric. Yammer metrics have 4 types: gauge, meter, histogram and timer. meter calculates a rate, but also exposes an acc

Re: [DISCUSS] KIP-794: Strictly Uniform Sticky Partitioner

Hi Jun, 30. Clarified. 31. I plan to do some benchmarking once implementation is finished, I'll update the KIP with the results once I have them. The reason to make it default is that it won't be used otherwise and we won't know if it's good or not in practical workloads. -Artem On Thu, Mar 1

Build failed in Jenkins: Kafka » kafka-2.6-jdk8 #147

See Changes: [Randall Hauch] KAFKA-12879: Revert changes from KAFKA-12339 and instead add retry capability to KafkaBasedLog (#11797) [Randall Hauch] KAFKA-12879: Addendum to reduce flakiness of tests

[GitHub] [kafka-site] guozhangwang merged pull request #399: Minor typo: "result is a" > "result in a"

guozhangwang merged pull request #399: URL: https://github.com/apache/kafka-site/pull/399 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsu

[jira] [Resolved] (KAFKA-12879) Compatibility break in Admin.listOffsets()

[ https://issues.apache.org/jira/browse/KAFKA-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-12879. --- Reviewer: Randall Hauch Resolution: Fixed > Compatibility break in Admin.listOffsets()

Re: [DISCUSS] KIP-794: Strictly Uniform Sticky Partitioner

Hi, Artem. Thanks for the reply. One more comment. 32. Do we need to add any new metric on the producer? For example, if partitioner.availability.timeout.ms is > 0, it might be useful to know the number of unavailable partitions. Thanks, Jun On Thu, Mar 10, 2022 at 12:46 PM Artem Livshits wro

Re: [DISCUSS] KIP-820: Extend KStream process with new Processor API

Thanks all! I agree with Matthias and Jon on going forward with the new `FixedKeyRecord` approach. The KIP has been updated accordingly. Feel free to add your vote or amend on the vote thread if needed. Cheers, On Mon, 7 Mar 2022 at 21:57, Matthias J. Sax wrote: > I think it's ok that we cann

[jira] [Created] (KAFKA-13727) Edge case in cleaner can result in premature removal of ABORT marker

Jason Gustafson created KAFKA-13727: --- Summary: Edge case in cleaner can result in premature removal of ABORT marker Key: KAFKA-13727 URL: https://issues.apache.org/jira/browse/KAFKA-13727 Project: K

Re: [DISCUSS] KIP-794: Strictly Uniform Sticky Partitioner

Hi Jun, 32. Good point. Do you think it's ok to defer the metrics until we run some benchmarks so that we get a better idea of what metrics we need? -Artem On Thu, Mar 10, 2022 at 3:12 PM Jun Rao wrote: > Hi, Artem. > > Thanks for the reply. One more comment. > > 32. Do we need to add any new

[jira] [Created] (KAFKA-13728) PushHttpMetricsReporter no longer pushes metrics when network failure is recovered.

XiaoyiPeng created KAFKA-13728: -- Summary: PushHttpMetricsReporter no longer pushes metrics when network failure is recovered. Key: KAFKA-13728 URL: https://issues.apache.org/jira/browse/KAFKA-13728 Proje

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

See Changes: -- [...truncated 553830 lines...] [2022-03-10T21:05:48.810Z] [2022-03-10T21:05:48.810Z] org.apache.kafka.streams.integration.TableTableJoinIntegrationTest >

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

See