Re: [DISCUSS] KIP-913: add new method to provide possibility for accelerate first record's sending

Hi Haruki Okada: Thanks for commenting more ideas. For the naming. Maybe it is personal view for which is better. For the Admin API's approach. it can't solve the issue for Producer's warmup and not every API can call the API with high permissions. For the approach: retry calling partitionsFor

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

See Changes: -- [...truncated 539852 lines...] [2023-03-09T05:06:25.857Z] [INFO] Parameter: version, Value: 0.1 [2023-03-09T05:06:25.857Z] [INFO] Parameter: groupId,

Re: [DISCUSS] KIP-913: add new method to provide possibility for accelerate first record's sending

Thanks for your explanation. > Thus, The code will look strange to call partitionsFor(topic) Hmm is that so? As the javadoc for `partitionsFor` states, it is simply for getting partition metadata for the topic, so I think nothing is strange even if we use it for "warmup" metadata. (And if so,

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

I repost the newly changed KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-842%3A+Add+richer+group+offset+reset+mechanisms hudeqi 16120...@bjtu.edu.cn写道： > Hello, have any mates who have discussed it before seen it? Also welcome new > mates to discuss together. > > hudeqi

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

Hello, have any mates who have discussed it before seen it? Also welcome new mates to discuss together. hudeqi 16120...@bjtu.edu.cn写道： > Long time no see, this issue has been discussed for a long time, now please > allow me to summarize this issue, and then everyone can help to see which >

Re: [DISCUSS] KIP-913: add new method to provide possibility for accelerate first record's sending

Hi Haruki Okada: There is another KIP912 discussion related to this one. Welcome to give some comments/suggestions. Thanks. I think if the 912 is done. New method getCluster can use the new config directly with time parameter removed. WDTY? [DISCUSS] KIP-912: Support decreasing send's block

Re: [DISCUSS] KIP-913: add new method to provide possibility for accelerate first record's sending

Hi Okada Haruki: Thanks for your comment. I can use it partitionsFor(topic) for the goal, thus there are two reasons why I don't choose it and propose to add new dedicated method: 1) Consider how to use the method to solve the issue, We should call it in application's startup process before any

Re: max.poll.interval.ms rebalance override

I overlooked the pause resume mechanism- it should work for us I think  On Wednesday, March 8, 2023, 4:52 PM, Mcs Vemuri wrote: Hello, Is there a way to override a rebalance caused by max.poll.interval.ms? We have a case where there are multiple consumers in the same group- but some of them

Re: [DISCUSS] KIP-913: add new method to provide possibility for accelerate first record's sending

You can just use Producer#partitionsFor 2023年3月9日(木) 11:13 jian fu : > Hi All: > > If anyone can help to give some comments or suggestions for the proposal. > Thanks in advance! > > Regards > Jian > > jian fu 于2023年3月6日周一 17:00写道： > > > Hi Everyone: > > Nice to meet you. > > > > I created one

Re: [DISCUSS] KIP-912: Support decreasing send's block time without worrying about metadata's fetch

Hi All: If anyone can help to give some comments or suggestions for the proposal. Thanks in advance! Regards Jian jian fu 于2023年3月6日周一 15:55写道： > Hi Everyone: > Nice to meet you. > > I created one KIP to request your review. > KIP-912: Support decreasing send's block time without worrying

Re: [DISCUSS] KIP-913: add new method to provide possibility for accelerate first record's sending

Hi All: If anyone can help to give some comments or suggestions for the proposal. Thanks in advance! Regards Jian jian fu 于2023年3月6日周一 17:00写道： > Hi Everyone: > Nice to meet you. > > I created one KIP to request your review. > KIP-913: add new method to provide possibility for accelerate

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

See

max.poll.interval.ms rebalance override

Hello, Is there a way to override a rebalance caused by max.poll.interval.ms? We have a case where there are multiple consumers in the same group- but some of them might start sooner than the rest and all consumers can be lazy pollers  The issue is that we need to set the poll interval to a

[jira] [Created] (KAFKA-14797) MM2 does not emit offset syncs when conservative translation logic exceeds positive max.offset.lag

Greg Harris created KAFKA-14797: --- Summary: MM2 does not emit offset syncs when conservative translation logic exceeds positive max.offset.lag Key: KAFKA-14797 URL: https://issues.apache.org/jira/browse/KAFKA-14797

[jira] [Created] (KAFKA-14796) Migrate ZK ACLs to KRaft

David Arthur created KAFKA-14796: Summary: Migrate ZK ACLs to KRaft Key: KAFKA-14796 URL: https://issues.apache.org/jira/browse/KAFKA-14796 Project: Kafka Issue Type: Sub-task

Re: [DISCUSS] KIP-911: Add source tag to MirrorSourceConnector metrics

Hi Chris, Thanks for taking a look at the KIP. I've removed the mention to the update mode. It was copied from somewhere else and I forgot to delete it. Thanks, Mickael On Wed, Mar 8, 2023 at 7:26 PM Chris Egerton wrote: > > Hi Mickael, > > Thanks for the KIP! LGTM. > > I find the rationales

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

See Changes: -- [...truncated 540947 lines...] [2023-03-08T21:07:23.511Z] Gradle Test Run :core:integrationTest > Gradle Test Executor 178 > ZkMigrationClientTest >

Re: [DISCUSS] KIP-908: Add description field to connector configuration

Hi Mickael, I do sympathize with the desire for a "quick fix". I think your point about these being problematic to support sums up my hesitation here pretty well, both with respect to the potential footgun of unintended rebalances (should users try to do more with this field than we expect), and

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.4 #94

See

Re: [DISCUSS] KIP-911: Add source tag to MirrorSourceConnector metrics

Hi Mickael, Thanks for the KIP! LGTM. I find the rationales for the rejected alternatives convincing, and agree with the deprecation plan and opt-in behavior for pre-4.0 releases. I also appreciate the historical context provided in the motivation section about why we don't already use a tag for

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1663

See

[jira] [Created] (KAFKA-14795) Provide message formatter for RemoteLogMetadata

Ivan Yurchenko created KAFKA-14795: -- Summary: Provide message formatter for RemoteLogMetadata Key: KAFKA-14795 URL: https://issues.apache.org/jira/browse/KAFKA-14795 Project: Kafka Issue

[jira] [Created] (KAFKA-14794) Unable to deserialize base64 JSON strings

José Armando García Sancio created KAFKA-14794: -- Summary: Unable to deserialize base64 JSON strings Key: KAFKA-14794 URL: https://issues.apache.org/jira/browse/KAFKA-14794 Project: Kafka

[jira] [Created] (KAFKA-14793) Propagate topic ids to the group coordinator

Alexandre Dupriez created KAFKA-14793: - Summary: Propagate topic ids to the group coordinator Key: KAFKA-14793 URL: https://issues.apache.org/jira/browse/KAFKA-14793 Project: Kafka Issue

Re: [Discuss] KIP-581: Value of optional null field which has default value

Hi, This KIP has been staled for a long time. Since it would be a useful feature, I pinged Cheng about a month ago asking if he was planning to work on it again. I've not received a reply, so I've allowed myself to update the KIP (hopefully preserving the initial requirements) and would like to

[jira] [Resolved] (KAFKA-14781) MM2 logs misleading error during topic ACL sync when broker does not have authorizer configured

[ https://issues.apache.org/jira/browse/KAFKA-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-14781. --- Fix Version/s: 3.5.0 Resolution: Fixed > MM2 logs misleading error during topic ACL

Re: [DISCUSS] KIP-882: Make Kafka Connect REST API request timeouts configurable

Hi Greg, Thanks for the response! 1. Hm that's a fair point, and while there aren't any strict guidelines or rules governing whether something should be a query parameter versus a request header, I agree that it might be more idiomatic for a request timeout value to be accepted via a custom

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

See

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

See Changes: -- [...truncated 542257 lines...] [2023-03-08T10:57:15.303Z] > Task :clients:compileTestJava UP-TO-DATE [2023-03-08T10:57:15.303Z] > Task :clients:testClasses