Re: [VOTE] KIP-618: Exactly-once support for source connectors

+1 (non-binding) On Thu, Jun 3, 2021, 10:23 AM Chris Egerton wrote: > Hi all, > > I'd like to call for a vote on KIP-618, which adds support for exactly-once > delivery guarantees for source connectors in the Kafka Connect framework. > > I suspect there might be a little more discussion to be

Re: [DISCUSS] KIP-655: Windowed "Distinct" Operation for KStream

Just skimmed over the thread -- first of all, I am glad that we could merge KIP-418 and ship it :) About the re-partitioning concerns, there are already two tickets for it: - https://issues.apache.org/jira/browse/KAFKA-4835 - https://issues.apache.org/jira/browse/KAFKA-10844 Thus, it seems

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

See Changes: -- [...truncated 473306 lines...] [2021-06-04T03:45:18.877Z] [2021-06-04T03:45:18.877Z] TopicCommandIntegrationTest >

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

See Changes: -- [...truncated 472601 lines...] [2021-06-04T01:29:52.582Z] > Task :clients:jar UP-TO-DATE [2021-06-04T01:29:52.582Z] > Task :server-common:compileJava

[jira] [Created] (KAFKA-12888) Add transaction tool

Jason Gustafson created KAFKA-12888: --- Summary: Add transaction tool Key: KAFKA-12888 URL: https://issues.apache.org/jira/browse/KAFKA-12888 Project: Kafka Issue Type: Sub-task

Re: [VOTE] KIP-726: Make the "cooperative-sticky, range" as the default assignor

Thanks Luke, I'm +1 on this proposal. Guozhang On Wed, Jun 2, 2021 at 8:16 PM Luke Chen wrote: > Hi all, > I'd like to call for a vote on KIP-726: Make the "cooperative-sticky, > range" as the default assignor. > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177048248 > >

[jira] [Created] (KAFKA-12887) Do not trigger user-customized ExceptionalHandler for RTE

Guozhang Wang created KAFKA-12887: - Summary: Do not trigger user-customized ExceptionalHandler for RTE Key: KAFKA-12887 URL: https://issues.apache.org/jira/browse/KAFKA-12887 Project: Kafka

Re: [DISCUSS] KIP-746: Revise KRaft Metadata Records

Quick question: given that upgrades are not supported, do we actually want to introduce a new version for the RPCs? Ismael On Wed, Jun 2, 2021 at 11:02 AM Colin McCabe wrote: > Hi all, > > I have posted a KIP about updating the KRaft metadata records for 3.0. > > Check it out at :

Re: [DISCUSS] KIP-746: Revise KRaft Metadata Records

On Thu, Jun 3, 2021, at 16:29, Jun Rao wrote: > Hi, Colin, > > Thanks for the KIP. Just a couple of minor comments. > Hi Jun, Thanks for taking a look. Sorry I just started the vote thread before I saw this! :) > 1. Fields like RemovingReplicas are added as tagged fields in >

[VOTE] KIP-746: Revise KRaft Metadata Records

Hi all, I'd like to call a vote for KIP-746: Revise KRaft Metadata Records. This is a minor KIP which revises the KRaft metadata records slightly for the upcoming 3.0 release. The KIP is at: https://cwiki.apache.org/confluence/x/34zOCg best, Colin

Re: [DISCUSS] KIP-746: Revise KRaft Metadata Records

Hi, Colin, Thanks for the KIP. Just a couple of minor comments. 1. Fields like RemovingReplicas are added as tagged fields in PartitionChangeRecord, but as non-tagged fields in PartitionRecord. Should we make them consistent? 2. Should we add BrokerRegistrationChangeRecord later when it has

Re: [DISCUSS] KIP-748: Add Broker Count Metrics

Hi Ryan, Thanks for the KIP. I think it would be good to provide the RegisteredBrokerCount metric for the ZK controller as well as for the Quorum controller. Looks good aside from that! best, Colin On Thu, Jun 3, 2021, at 14:09, Ryan Dielhenn wrote: > Hey kafka-dev, > > I created KIP-748 as

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

See Changes: -- [...truncated 405148 lines...] [2021-06-03T22:38:02.534Z] KafkaZkClientTest > testConditionalUpdatePath() PASSED [2021-06-03T22:38:02.534Z]

[jira] [Created] (KAFKA-12886) Enable request forwarding by default in 3.0

Jason Gustafson created KAFKA-12886: --- Summary: Enable request forwarding by default in 3.0 Key: KAFKA-12886 URL: https://issues.apache.org/jira/browse/KAFKA-12886 Project: Kafka Issue

[DISCUSS] KIP-748: Add Broker Count Metrics

Hey kafka-dev, I created KIP-748 as a proposal to add broker count metrics to the Quorum Controller. https://cwiki.apache.org/confluence/display/KAFKA/KIP-748%3A+Add+Broker+Count+Metrics#KIP748:AddBrokerCountMetrics Best, Ryan Dielhenn

Re: [VOTE] KIP-738: Removal of Connect's internal converter properties

+1 (binding). Thanks Chris! On Wed, Jun 2, 2021 at 11:00 PM Randall Hauch wrote: > Thanks for putting this together, Chris. > > Technically, we don't need a new KIP to explicitly remove an API, config, > etc. that was previously deprecated under an earlier approved KIP. But > KIP-174 could

Re: [DISCUSS] KIP-745: Connect API to restart connector and tasks

Agreed, this would be a great enhancement. On Thu, Jun 3, 2021 at 9:26 AM Nikita Kretov wrote: > Hello! It's really not intuitive that you need to restart connect and > tasks separately! I'd like to see this KIP landed in 3.0.0 release! > > On 6/2/21 7:40 PM, Randall Hauch wrote: > > Hello all,

Re: Proposed breaking changes for Connect in AK 3.0.0

I've updated the proposal for 3.0 [1] with the following changes: - Remove the `rest.host.name` and `rest.port` worker config properties deprecated way back in AK 1.1, which was released over three years ago in Mar 2018. - Mention KIP-738 for removal of the internal worker configs

[VOTE] KIP-618: Exactly-once support for source connectors

Hi all, I'd like to call for a vote on KIP-618, which adds support for exactly-once delivery guarantees for source connectors in the Kafka Connect framework. I suspect there might be a little more discussion to be had but with the KIP freeze deadline approaching, I wanted to give anyone

Kafka EOL policy

Hi, I have a question about the EOL policy in the link at the end. The paragraph below from the link says the releases in the past year will be supported. The 3 releases from last year 2020 are 2.5 in Mar, 2.6 in June and 2.7 in Nov. We have in this year 2021 2.8 in April, 3.0 in July and

Re: [DISCUSS] KIP-745: Connect API to restart connector and tasks

Hello! It's really not intuitive that you need to restart connect and tasks separately! I'd like to see this KIP landed in 3.0.0 release! On 6/2/21 7:40 PM, Randall Hauch wrote: Hello all, Many users struggle with the connector restart REST API only restarting the Connector instance rather

[jira] [Created] (KAFKA-12885) Add the --timeout property to kafka-leader-election.sh

loboxu created KAFKA-12885: -- Summary: Add the --timeout property to kafka-leader-election.sh Key: KAFKA-12885 URL: https://issues.apache.org/jira/browse/KAFKA-12885 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-12884) Remove "--zookeeper" in system tests

Luke Chen created KAFKA-12884: - Summary: Remove "--zookeeper" in system tests Key: KAFKA-12884 URL: https://issues.apache.org/jira/browse/KAFKA-12884 Project: Kafka Issue Type: Sub-task

Re: Best Tool : Apache kafka Monitoring

Hello. Prometheus + grafana is a standard stack for metric collection and monitoring. Jmx exporter is a good metrics exporter for broker\zookeeper. Maybe you can take advantage from some additional exporters like linkeding burrow too. On 6/3/21 10:29 AM, Girish L wrote: Hello Apache Kafka

Best Tool : Apache kafka Monitoring

Hello Apache Kafka Experts, What is the best free tool for Apache kafka monitoring at enterprise level , with UI for admin team /support team? Could you please suggest something? Any links/ pointers Thanks

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

See