Re: [VOTE] 0.11.0.0 RC2

This vote passes with 7 +1 votes (3 binding) and no 0 or -1 votes. +1 votes PMC Members: Jun, Gwen, Guozhang Committers: Jason, Ismael Community: Tom Crayford, Jeff Chao 0 votes: none -1 votes: none Thanks to everyone who tested, voted and/or contributed to the release. I'll continue with the

0.11.0.0 RC2 Vote

My vote on the original VOTE thread somehow cannot show up, I have tried several ways and nothing works. So I am sending it as a new email which should belong to this thread:

Re: Weird broker lock-up causing an almost global downtime

Thanks Vincent. That's a good start for now. If you get a chance to forward some logs that would be great. -Bill On Tue, Jun 27, 2017 at 6:10 PM, Vincent Rischmann wrote: > Sure. > > The application reads a topic of keyless events and based on some > criteria of the

Re: Weird broker lock-up causing an almost global downtime

Sure. The application reads a topic of keyless events and based on some criteria of the event, it creates a new key and uses that for `selectKey`. Then I groupByKey and count with 3 differents windows. Each count is then stored in a database. The three windows are tumbling windows: - 1 minute

Re: Weird broker lock-up causing an almost global downtime

Hi Vincent, Thanks for reporting this. Could you give some details on your setup (topics, partitions and the structure of your streams application) so I can attempt to reproduce the issue? Thanks! On 2017-06-27 14:46 (-0400), Vincent Rischmann wrote: > Hello. so I had a

Re: Weird broker lock-up causing an almost global downtime

Hi Vincent, Thanks for reporting this issue. Could you give us some more details (number topics, partitions per topic and the structure of your Kafka Streams application) so we attempt to reproduce and diagnose the issue? Thanks! Bill On 2017-06-27 14:46 (-0400), Vincent Rischmann

Re: Weird broker lock-up causing an almost global downtime

On 2017-06-27 14:46 (-0400), Vincent Rischmann wrote: > Hello. so I had a weird problem this afternoon. I was deploying a > streams application and wanted to delete already existing internal > states data so I ran kafka-streams-application-reset.sh to do it, as >

Re: [ERICSSON] - Trade Compliance: ECCN code for Apache Items

I appreciate there may be a loss of subtlety traversing languages, but this doesn't come over to politely. I can't help you, the best I can find is . This *may* be more helpful than posting here although it covers none of the software you mention, sorry,

Weird broker lock-up causing an almost global downtime

Hello. so I had a weird problem this afternoon. I was deploying a streams application and wanted to delete already existing internal states data so I ran kafka-streams-application-reset.sh to do it, as recommended. it wasn't the first time I ran it and it had always worked before, in staging or in

Re: question about document

Correct. The use of the word "server" in that sentence is meant as broker (or KafkaServer as it shows up in the 'jps' command) not as a physical or virtual machine. -hans > On Jun 27, 2017, at 1:22 AM, James <896066...@qq.com> wrote: > > Hello, >At https://kafka.apache.org/intro, I found

Re: [VOTE] 0.11.0.0 RC2

Hi Gwen, Thanks for verifying the release candidate. Regarding KAFKA-4815, the thought did occur to me. However, I was not keen on moving all the subtasks that are not completed to another issue. Since you asked, I have done so though. :) Ismael On Tue, Jun 27, 2017 at 6:40 AM, Gwen Shapira

question about document

Hello, At https://kafka.apache.org/intro, I found a sentence: Each partition has one server which acts as the "leader" and zero or more servers which act as "followers". In my opinion, it is possible that more than one brokers exist on a machine with different ports and different

Re: Kafka Stream invalid partitions

Thanks Eno, for the info!. I will try your suggestion. 2017-06-27 14:04 GMT+02:00 Eno Thereska : > Thanks. I believe we’ve addressed this issue in 0.10.2.1, any chance you > could try that? > > Thanks > Eno > > On Jun 27, 2017, at 11:14 AM, D Stephan

Re: [VOTE] 0.11.0.0 RC2

Thanks Jeff, that's helpful. To be clear, this should not affect the Java client (max.request.size = 1 MB) or librdkafka-based clients (message.max.bytes = 1MB) with the default settings. I'm a bit surprised that Sarama doesn't have a similar mechanism. Seems like we'll have to live with that.

Re: Kafka Stream invalid partitions

Thanks. I believe we’ve addressed this issue in 0.10.2.1, any chance you could try that? Thanks Eno > On Jun 27, 2017, at 11:14 AM, D Stephan wrote: > > Hello, > > Thanks for your reply. > > I use Kafka & KafkaStream version 0.10.2.0. > Between the runs, the number of

Re: Kafka Stream invalid partitions

Hello, Thanks for your reply. I use Kafka & KafkaStream version 0.10.2.0. Between the runs, the number of partitions are not intentionally changed programmatically or manually. This topic: "external-batch-request-store-repartition" is an internally generated topic from this KafkaStream DSL

Re: Kafka Stream invalid partitions

Hi there, Thanks for the report. What version of Kafka are you using? Also, between runs do you change the number of partitions for your topics? I’m trying to figure out how this problem happens, any information on what is changing in between runs is appreciated. Thanks, Eno > On Jun 27,

kafka producer latency

Hi, I have a problem with the latency of my kafka producer under some circumstances. We are running three kafka brokers on version 0.10.2.0 and 3 zookeepers on version 3.4.8. The server properties are below, the main producer property that we change is that we require acks=all, so at least 2

Re: Exposing Kafka Topic to External Parties

So is it in general a good idea to ask my clients who are out of my IT infrastructure to directly write to my Topic? I'm seeing this as an anti-pattern. What do you guys think? On Mon, Jun 26, 2017 at 8:15 PM, Samuel Taylor wrote: > Hi Joe, > > For #2, if brokers and

Kafka Stream invalid partitions

Hello, When I use KafkaStreams DSL GroupByKey and Aggregate APIs, I have randomly & frequently below exceptions: In my opinion, it is not practical to clean up the invalid partitions everydays. For your information, this partition is an internal partition that automatically created by