Re: Customizing initial consumer group rebalance delay

Hello Boyang, Your observation is valid, in fact after KIP-134 is merged there are some discussions about on the voting thread as well, that whether we should better make it a client config than a global broker-level config. There are some general ideas grooming to further improve consumer

Re: [DISCUSS] - KIP-314: KTable to GlobalKTable Bi-directional Join

Hello Adam, Sorry for being late on this thread. I've read through your updated wiki and here are some thoughts: * I agree with your assessed impediments. In fact, today although the Global KTable have its own checkpoint files, and restoration process, during its restoration it will always try

[jira] [Created] (KAFKA-7126) Reduce number of rebalance period for large consumer groups after a topic is created

Dong Lin created KAFKA-7126: --- Summary: Reduce number of rebalance period for large consumer groups after a topic is created Key: KAFKA-7126 URL: https://issues.apache.org/jira/browse/KAFKA-7126 Project:

Re: [DISCUSS] KIP-328: Ability to suppress updates for KTables

Hi John, Regarding the metrics: yeah I think I'm with you that the dropped records due to window retention or emit suppression policies should be recorded differently, and using this KIP's proposed metric would be fine. If you also think we can use this KIP's proposed metrics to cover the window

Re: [DISCUSS] KIP-291: Have separate queues for control requests and data requests

Hey Lucas, Thanks much for the detailed documentation of the experiment. Initially I also think having a separate queue for controller requests is useful because, as you mentioned in the summary section of the Google doc, controller requests are generally more important than data requests and we

Re: Help with first contribution

Hello, Matthias. Thank you! I took this ticket. В Вс, 01/07/2018 в 18:10 -0700, Matthias J. Sax пишет: > How about this: https://issues.apache.org/jira/browse/KAFKA-7125 > > -Matthias > > On 6/28/18 8:31 AM, Nikolay Izhikov wrote: > > Hello, Matthias! > > > > > Did you filter for JIRAs with

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

For what I understood, that KIP is related to how KStreams will handle KTable updates in Windowed scenarios to optimize resource usage. I couldn't see any specific relation to this KIP. Had you? -Flávio Stutz On 2018/06/29 18:14:46, "Matthias J. Sax" wrote: > Flavio, > > thanks for cleaning

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

> I agree with Guozhang on comparing the pros and cons of the approach he > outlined vs the one in the proposed KIP. I've just replied him. Please take a look. > Will the triggering mechanism always be time, or would it make sense to > expand to use other mechanisms such as the number of records,

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

Cons: We tried the "single partition" strategy, but the problem is that for each incoming message to the Graph, we have another output message with the aggregated (cummulative or not) result, so that if we have a million messages/s (among all parallel tasks) being processed, we'll have another

Customizing initial consumer group rebalance delay

Hey there, I have a question regarding KIP-134. Basically this config `group.initial.rebalance.delay.ms` is set on broker side to delay the initial rebalance of consumer groups. For certain

Re: Help with first contribution

How about this: https://issues.apache.org/jira/browse/KAFKA-7125 -Matthias On 6/28/18 8:31 AM, Nikolay Izhikov wrote: > Hello, Matthias! > >> Did you filter for JIRAs with label "newbie" or "beginner"? > > "newbie" as it mentioned in "how to contribute" guide. > Seems, many of them already

[jira] [Created] (KAFKA-7125) Calling StreamsBuilderbuilder.build().describe() causes java.util.NoSuchElementException: null

Jouni created KAFKA-7125: Summary: Calling StreamsBuilderbuilder.build().describe() causes java.util.NoSuchElementException: null Key: KAFKA-7125 URL: https://issues.apache.org/jira/browse/KAFKA-7125

Re: [kafka-clients] Re: [VOTE] 1.0.2 RC1

+1 (non-binding) Verified tests, quick start, producer/consumer perf tests. On Sun, Jul 1, 2018 at 11:27 PM Ismael Juma wrote: > +1 (binding) > > Verified signature of source artifact, ran tests and verified quickstart > on source artifact with Java 7, verified quickstart on binary artifact

Re: [kafka-clients] Re: [VOTE] 0.11.0.3 RC0

+1 (non-binding) Verified quick start, ran producer/consumer perf tests, Thanks On Sun, Jul 1, 2018 at 8:29 PM Ismael Juma wrote: > +1 (binding) > > Verified signature of source artifact, ran tests and verified quickstart > on source artifact with Java 7, verified quickstart on binary

Re: [VOTE] 1.0.2 RC1

+1 (binding) Verified signature of source artifact, ran tests and verified quickstart on source artifact with Java 7, verified quickstart on binary artifact (Scala 2.12) with Java 8, sanity checked release notes and Maven staging repository. Ismael On Fri, Jun 29, 2018 at 10:02 PM Matthias J.

[DISCUSS] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

hi folks, KIP-331 is waiting for any suggestions, feedback and reviews. The main purpose of the KIP-331 is to add empty implementations to the close() and configure() so as to user can write less code to develop custom Serialzier, Deserializer and Serde. Cheers, Chia-Ping

Re: [VOTE] 0.11.0.3 RC0

+1 (binding) Verified signature of source artifact, ran tests and verified quickstart on source artifact with Java 7, verified quickstart on binary artifact (Scala 2.11) with Java 7, sanity checked release notes and Maven staging repository. Thanks for running the release! Ismael On Fri, Jun

[jira] [Resolved] (KAFKA-3571) Traits for utilities like ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3571. -- Resolution: Won't Fix Now AdminClient has support for most of the admin API. This can be used for

[jira] [Resolved] (KAFKA-7124) Number of AnyLogDir should match the length of the replicas list

[ https://issues.apache.org/jira/browse/KAFKA-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved KAFKA-7124. --- Resolution: Not A Problem > Number of AnyLogDir should match the length of the replicas list >

[jira] [Resolved] (KAFKA-7123) Documentation: broken link http://confluent.io/docs/current/kafka-rest/docs/intro.html

[ https://issues.apache.org/jira/browse/KAFKA-7123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7123. -- Resolution: Fixed > Documentation: broken link >

[jira] [Resolved] (KAFKA-4122) Consumer startup swallows DNS resolution exception and infinitely retries

[ https://issues.apache.org/jira/browse/KAFKA-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4122. -- Resolution: Duplicate Fixed under KAFKA-7111. > Consumer startup swallows DNS resolution exception

[jira] [Created] (KAFKA-7124) Number of AnyLogDir should match the length of the replicas list

Ted Yu created KAFKA-7124: - Summary: Number of AnyLogDir should match the length of the replicas list Key: KAFKA-7124 URL: https://issues.apache.org/jira/browse/KAFKA-7124 Project: Kafka Issue