Re: [DISCUSSION] KIP-864: Support --bootstrap-server in kafka-streams-application-reset

Hello Николай, Thanks for writing the KIP, I think it's rather straightforward and better to be consistent in tooling params. I'm +1. Guozhang On Mon, Sep 5, 2022 at 11:25 PM Николай Ижиков wrote: > Hello. > > Do we still want to make parameter names consistent in tools? > If yes, please,

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hello David, One of Jun's comments make me thinking: ``` In this case, a new assignment is triggered by the client side assignor. When constructing the HB, the consumer will always consult the client side assignor and propagate the information to the group coordinator. In other words, we don't

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

See Changes: -- [...truncated 504935 lines...] [2022-09-09T04:37:27.990Z] StreamsAssignmentScaleTest > testStickyTaskAssignorLargePartitionCount PASSED

[jira] [Resolved] (KAFKA-14210) client quota config key is sanitized in Kraft broker

[ https://issues.apache.org/jira/browse/KAFKA-14210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dengziming resolved KAFKA-14210. Resolution: Not A Problem > client quota config key is sanitized in Kraft broker >

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

See Changes: -- [...truncated 503685 lines...] [2022-09-09T02:05:19.464Z] [2022-09-09T02:05:19.464Z] StreamsAssignmentScaleTest >

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.3 #62

See Changes: -- [...truncated 571971 lines...] [2022-09-09T02:00:20.285Z] [2022-09-09T02:00:20.285Z]

[jira] [Created] (KAFKA-14210) client quota config key is sanitized in Kraft broker

dengziming created KAFKA-14210: -- Summary: client quota config key is sanitized in Kraft broker Key: KAFKA-14210 URL: https://issues.apache.org/jira/browse/KAFKA-14210 Project: Kafka Issue

Re: [DISCUSS] KIP-857: Streaming recursion in Kafka Streams

Hello Nick, Thanks for the patient explanations. I think I'm convinced that we should not exclude repartitioning inside the recursive operator indeed, and in fact we cannot programmingly forbid it by the UnaryOperator itself anyways. Just a few nits on the page itself: 1) could you still

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

See Changes: -- [...truncated 504255 lines...] [2022-09-08T23:23:54.645Z] [2022-09-08T23:23:54.645Z] KStreamAggregationIntegrationTest >

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.3 #61

See Changes: -- [...truncated 572655 lines...] [2022-09-08T18:03:11.401Z] [2022-09-08T18:03:11.401Z]

[jira] [Resolved] (KAFKA-14204) QuorumController must correctly handle overly large batches

[ https://issues.apache.org/jira/browse/KAFKA-14204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jose Armando Garcia Sancio resolved KAFKA-14204. Resolution: Fixed > QuorumController must correctly handle overly

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

See Changes: -- [...truncated 502535 lines...] [2022-09-08T20:58:08.436Z] [2022-09-08T20:58:08.436Z] StreamsAssignmentScaleTest >

Re: [VOTE] KIP-862: Self-join optimization for stream-stream joins

Thanks Vicky, I read through the KIP again and it looks good to me. Just a quick question regarding the public config changes: you mentioned "No public interfaces will be impacted. The config TOPOLOGY_OPTIMIZATION_CONFIG will be extended to accept a list of optimization rule configs in addition

[jira] [Resolved] (KAFKA-14143) Exactly-once source system tests

[ https://issues.apache.org/jira/browse/KAFKA-14143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-14143. --- Resolution: Fixed > Exactly-once source system tests > > >

[VOTE] KIP-862: Self-join optimization for stream-stream joins

Hello everyone, I'd like to open the vote for KIP-862, which proposes to optimize stream-stream self-joins by using a single state store for the join. The proposal is here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-862%3A+Self-join+optimization+for+stream-stream+joins Thanks to all

[jira] [Created] (KAFKA-14209) Optimize stream stream self join to use single state store

Vicky Papavasileiou created KAFKA-14209: --- Summary: Optimize stream stream self join to use single state store Key: KAFKA-14209 URL: https://issues.apache.org/jira/browse/KAFKA-14209 Project:

Re: [VOTE] KIP-854 Separate configuration for producer ID expiry

Hi all, Thanks for voting on this KIP! Taking a look at this change, I realized that rolling the cluster to apply the configuration may be difficult when the issue is ongoing. The brokers will become overloaded and it will be hard to roll. Since the configuration can be dynamic, it makes sense

Bug fix for KAFKA-13927

Hello, I have a relatively simple fix for the bug reported in KAFKA-13927 in which Connect will not commit offsets for a message that a SinkTask retries and eventually succeeds. Would appreciate eyes

Re: Last sprint to finish line: Replace EasyMock/Powermock with Mockito

Thanks Christo for the updates. As we are adding new unit tests we are also keen on using the new Mockito packages and so far I'd like to say it's much easier to use :) would chime in to help on reviewing some of the PRs as well. Guozhang On Tue, Sep 6, 2022 at 11:02 PM Christo Lolov wrote: >

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

See Changes: -- [...truncated 421951 lines...] [2022-09-08T17:12:48.253Z] [2022-09-08T17:12:48.253Z] FineGrainedAutoResetIntegrationTest >

[jira] [Resolved] (KAFKA-13952) Infinite retry timeout is not working

[ https://issues.apache.org/jira/browse/KAFKA-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-13952. --- Fix Version/s: 3.4.0 Resolution: Fixed > Infinite retry timeout is not working >

[DISCUSS] KIP-793: Sink Connectors: Support topic-mutating SMTs for async connectors (preCommit users)

Hi all, I would like to (re)start a new discussion thread on KIP-793 (Kafka Connect) which proposes some additions to the public SinkRecord interface in order to support topic mutating SMTs for sink connectors that do their own offset tracking. Links: KIP:

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

Great. I have updated the KIP to reflect this. Cheers, Jorge. On Thu, 8 Sept 2022 at 12:26, Yash Mayya wrote: > Thanks, I think it makes sense to define these metrics at a DEBUG recording > level. > > On Thu, Sep 8, 2022 at 2:51 PM Jorge Esteban Quilcate Otoya < > quilcate.jo...@gmail.com>

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

See Changes: -- [...truncated 505057 lines...] [2022-09-08T12:16:10.738Z] [2022-09-08T12:16:10.738Z] IQv2IntegrationTest > shouldFetchExplicitlyFromAllPartitions()

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

Thanks, I think it makes sense to define these metrics at a DEBUG recording level. On Thu, Sep 8, 2022 at 2:51 PM Jorge Esteban Quilcate Otoya < quilcate.jo...@gmail.com> wrote: > On Thu, 8 Sept 2022 at 05:55, Yash Mayya wrote: > > > Hi Jorge, > > > > Thanks for the changes. With regard to

[jira] [Created] (KAFKA-14208) KafkaConsumer#commitAsync throws unexpected WakeupException

Qingsheng Ren created KAFKA-14208: - Summary: KafkaConsumer#commitAsync throws unexpected WakeupException Key: KAFKA-14208 URL: https://issues.apache.org/jira/browse/KAFKA-14208 Project: Kafka

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

On Thu, 8 Sept 2022 at 05:55, Yash Mayya wrote: > Hi Jorge, > > Thanks for the changes. With regard to having per batch vs per record > metrics, the additional overhead I was referring to wasn't about whether or > not we would need to iterate over all the records in a batch. I was > referring to