Build failed in Jenkins: kafka-trunk-jdk11 #413

See Changes: [cshapi] MINOR: Comment spelling nit -- [...truncated 2.35 MB...] org.apache.kafka.connect.data.ValuesTest > shouldFailToParseStringOfMapWithIntValuesWithBl

Build failed in Jenkins: kafka-trunk-jdk8 #3503

See Changes: [github] MINOR: Move KTable source topic for changelog to optimization framework [colin] KAFKA-8034: Use automatic RPC generation in DeleteTopics [cshapi] MINOR: Optimize ConnectionStressWorker [c

Re: [DISCUSS] KIP-429 : Smooth Auto-Scaling for Kafka Streams

Bump up on this discussion thread. I've added a few new drawings for better illustration, would really appreciate your feedbacks. Guozhang On Wed, Mar 20, 2019 at 6:17 PM Guozhang Wang wrote: > Hello Boyang, > > I've made another thorough pass over this KIP and I'd like to spilt it > into two

Jenkins build is back to normal : kafka-trunk-jdk8 #3502

See

[jira] [Resolved] (KAFKA-4600) Consumer proceeds on when ConsumerRebalanceListener fails

[ https://issues.apache.org/jira/browse/KAFKA-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4600. -- Resolution: Fixed Fix Version/s: 0.11.0.0 > Consumer proceeds on when ConsumerRebalanceL

[DISCUSS] KIP-445: In-memory Session Store

Hello all, This KIP proposes adding an in-memory session store to round-out the API and support built-in persistent and in-memory versions of ALL store types. Any feedback is appreciated https://cwiki.apache.org/confluence/display/KAFKA/KIP-445%3A+In-memory+Session+Store I made a first pass at a

[jira] [Resolved] (KAFKA-4799) session timeout during event processing shuts down stream

[ https://issues.apache.org/jira/browse/KAFKA-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4799. -- Resolution: Fixed Fix Version/s: 0.11.0.1 > session timeout during event processing shut

[jira] [Resolved] (KAFKA-6631) Kafka Streams - Rebalancing exception in Kafka 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6631. -- Resolution: Fixed Just a side note that we are working on KAFKA-7149 to reduce the assignment

[jira] [Resolved] (KAFKA-7142) Rebalancing large consumer group can block the coordinator broker for several seconds

[ https://issues.apache.org/jira/browse/KAFKA-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7142. -- Resolution: Fixed Fix Version/s: 2.1.0 Resolving the ticket since the PR is merged as in

[jira] [Resolved] (KAFKA-6681) Two instances of kafka consumer reading the same partition within a consumer group

[ https://issues.apache.org/jira/browse/KAFKA-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6681. -- Resolution: Fixed Fix Version/s: 0.11.0.0 Resolving as part of https://issues.apache.org

Re: Contributor list

Hi, Arun, Thanks for your interest. I just added arao7676 to the contribution list. Jun On Fri, Mar 29, 2019 at 3:05 PM Arun Rao wrote: > Can you please add me to the contributors list? I would like to start > contributing to Kafka project. > > Thank you > arun >

Contributor list

Can you please add me to the contributors list? I would like to start contributing to Kafka project. Thank you arun

Re: [VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

Ah I see, my bad :) Yes that was the documented value in `TopicConfig`, and I agree we should just change that as well. Will update the KIP. On Fri, Mar 29, 2019 at 11:27 AM Mickael Maison wrote: > Hi Guozhang, > > I know the KIP is about segments configuration but I'm talking about > retenti

Re: [VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

Hi Guozhang, I know the KIP is about segments configuration but I'm talking about retention.ms which is also explicitly set on repartition topics https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/processor/internals/RepartitionTopicConfig.java#L39 Streams is

[DISCUSS] KIP-444: Augment Metrics for Kafka Streams

Hello folks, I'd like to propose the following KIP to improve the Kafka Streams metrics mechanism to users. This includes 1) a minor change in the public StreamsMetrics API, and 2) a major cleanup on the Streams' own built-in metrics hierarchy. Details can be found here: https://cwiki.apache.org

Re: [VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

Hello Mickael, segment.ms default value in TopicConfig is 7 days, I think this is a sufficient default value. Do you have any motivations to set it to -1? Guozhang On Fri, Mar 29, 2019 at 9:42 AM Mickael Maison wrote: > +1 (non binding) > For consistency, should we also set retention.ms to -1

Re: [VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

Thanks for the KIP, +1 (binding) -Bill On Fri, Mar 29, 2019 at 12:42 PM Mickael Maison wrote: > +1 (non binding) > For consistency, should we also set retention.ms to -1 instead of > Long.MAX_VALUE? > > On Fri, Mar 29, 2019 at 3:59 PM Manikumar > wrote: > > > > +1 (binding) > > > > Thanks fo

Re: [DISCUSS] KIP-433: Provide client API version to authorizer

Hi Ying, That's a fair point. Maybe using API keys directly is reasonable here. One thing that's probably worth calling out is that if we make the name part of the configuration, we can't rename APIs in the future. That's probably OK as long as it's documented. best, Colin On Thu, Mar 28, 2

Re: [VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

+1 (non binding) For consistency, should we also set retention.ms to -1 instead of Long.MAX_VALUE? On Fri, Mar 29, 2019 at 3:59 PM Manikumar wrote: > > +1 (binding) > > Thanks for the KIP. > > On Fri, Mar 29, 2019 at 9:04 PM Damian Guy wrote: > > > +1 > > > > On Fri, 29 Mar 2019 at 01:59, John R

Re: [VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

+1 (binding) Thanks for the KIP. On Fri, Mar 29, 2019 at 9:04 PM Damian Guy wrote: > +1 > > On Fri, 29 Mar 2019 at 01:59, John Roesler wrote: > > > +1 (nonbinding) from me. > > > > On Thu, Mar 28, 2019 at 7:08 PM Guozhang Wang > wrote: > > > > > Hello folks, > > > > > > I'd like to directly s

Re: [VOTE] KIP-443: Return to default segment.ms and segment.index.bytes in Streams repartition topics

+1 On Fri, 29 Mar 2019 at 01:59, John Roesler wrote: > +1 (nonbinding) from me. > > On Thu, Mar 28, 2019 at 7:08 PM Guozhang Wang wrote: > > > Hello folks, > > > > I'd like to directly start a voting thread on this simple KIP to change > the > > default override values for repartition topics: >

Re: [VOTE] KIP-422: Use the default value of max.poll.interval in Streams

+1 On Wed, 27 Mar 2019 at 21:38, John Roesler wrote: > Ah, good point, Guozhang. I'll remove that mention from the KIP. > > On Wed, Mar 27, 2019 at 3:30 PM Bill Bejeck wrote: > > > +1 for me, > > > > Thanks, > > Bill > > > > On Wed, Mar 27, 2019 at 4:13 PM Guozhang Wang > wrote: > > > > > +1 f

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

Hi Paul! I read your code carefully and now I am fully convinced: your proposal looks better and should work. We just have to document the crucial fact that KStream consumers are invoked as they're added. And then it's all going to be very nice. What shall we do now? I should re-write the KI

Build failed in Jenkins: kafka-trunk-jdk8 #3501

See Changes: [wangguoz] MINOR: Streams input topic corrected (#6513) -- [...truncated 4.71 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldPunctuateOnStrea

[jira] [Created] (KAFKA-8175) The broker block some minutes may occur expired error message for a period of time

huangyiming created KAFKA-8175: -- Summary: The broker block some minutes may occur expired error message for a period of time Key: KAFKA-8175 URL: https://issues.apache.org/jira/browse/KAFKA-8175 Projec