[VOTE] 1.0.0 RC0

Hello Kafka users, developers and client-developers, This is the first candidate for release of Apache Kafka 1.0.0. It's worth noting that starting in this version we are using a different version protocol with three digits: *major.minor.bug-fix* Any and all testing is welcome, but the

Re: Kafka cluster Error

"Unable to connect" Try pinging and running ZK cli commands on one of the ZKs from the Kafka Broker that is failing to come up. On Tue, Oct 10, 2017 at 3:35 PM, Kannappan, Saravanan (Contractor) < saravanan_kannap...@comcast.com> wrote: > Hello, Someone can you help me kafka server not starting

Re: Kafka cluster Error

The error seems pretty obvious. Is your zookeeper address correct and is it running? On Tue, Oct 10, 2017 at 3:35 PM, Kannappan, Saravanan (Contractor) < saravanan_kannap...@comcast.com> wrote: > Hello, Someone can you help me kafka server not starting after rebooting , > the below is the error

Re: Kafka cluster Error

Can you check the health of zookeeper quorum ? Cheers On Tue, Oct 10, 2017 at 3:35 PM, Kannappan, Saravanan (Contractor) < saravanan_kannap...@comcast.com> wrote: > Hello, Someone can you help me kafka server not starting after rebooting , > the below is the error message > > [2017-10-10

Kafka cluster Error

Hello, Someone can you help me kafka server not starting after rebooting , the below is the error message [2017-10-10 22:25:25,365] INFO shutting down (kafka.server.KafkaServer) [2017-10-10 22:25:25,374] INFO shut down completed (kafka.server.KafkaServer) [2017-10-10 22:25:25,375] FATAL Fatal

Re: kafka-streams dying if can't create internal topics

Thanks Matthias, here is issue: https://issues.apache.org/jira/browse/KAFKA-6047 On Tue, Oct 10, 2017 at 8:50 PM, Matthias J. Sax wrote: > https://issues.apache.org/jira/browse/KAFKA-1?jql=project%20%3D%20KAFKA > > Or just put "apache kafka jira" into your favorite

Re: Kafka 0.10: Two Kafka Consumers, two different topics, same group ID - commit exception occurs

Why do you use the same groupId? This sound not correct. You would use a consumer group to share load of a single topic based on partitions. Ie. if a topic has multiple partitions, different partitions are processed by different consumer within the same group. But in your case, the second

Re: kafka-streams dying if can't create internal topics

https://issues.apache.org/jira/browse/KAFKA-1?jql=project%20%3D%20KAFKA Or just put "apache kafka jira" into your favorite search engine... -Matthias On 10/10/17 10:48 AM, Dmitriy Vsekhvalnov wrote: > Hi Matthias, > > thanks. Would you mind point me to correct Jira URL where i can file an >

Re: kafka-streams dying if can't create internal topics

Hi Matthias, thanks. Would you mind point me to correct Jira URL where i can file an issue? Thanks again. On Tue, Oct 10, 2017 at 8:38 PM, Matthias J. Sax wrote: > Yes, please file a Jira. We need to fix this. Thanks a lot! > > -Matthias > > On 10/10/17 5:24 AM, Dmitriy

Re: Getting started with stream processing

Hi, if the aggregation returns a different type, you can use .aggregate(...) instead of .reduce(...) Also, for you time based computation, did you consider to use windowing? -Matthias On 10/10/17 6:27 AM, RedShift wrote: > Hi all > > Complete noob with regards to stream processing, this is

Re: kafka-streams dying if can't create internal topics

Yes, please file a Jira. We need to fix this. Thanks a lot! -Matthias On 10/10/17 5:24 AM, Dmitriy Vsekhvalnov wrote: > Hi all, > > still doing disaster testing with Kafka cluster, when crashing several > brokers at once sometimes we observe exception in kafka-stream app about > inability to

Re: Serve interactive queries from standby replicas

Thanks! On 10/9/17 1:27 PM, Stas Chizhov wrote: > Hi, > > I have created a ticker: https://issues.apache.org/jira/browse/KAFKA-6031 > > Best regards, > Stas. > > 2017-10-06 23:39 GMT+02:00 Guozhang Wang : > >> Hi Stas, >> >> Would you mind creating a JIRA for this

Re: Add Kafka user list

If you want to subscribe follow instructions here: http://kafka.apache.org/contact On 10/10/17 2:07 AM, shawnding(丁晓坤) wrote: > Add Kafka user list > signature.asc Description: OpenPGP digital signature

Add Kafka user list

Add Kafka user list

Custom converter with Kafka Connect ?

Hello, I'm trying to use a custom converter with Kafka Connect and I cannot seem to get it right. I'm hoping someone has experience with this and could help me figure it out ! Initial situation - my custom converter's class path is 'custom.CustomStringConverter'. - to avoid

Getting started with stream processing

Hi all Complete noob with regards to stream processing, this is my first attempt. I'm going to try and explain my thought process, here's what I'm trying to do: I would like to create a sum of "load" for every hour, for every device. Incoming stream of data:

RE: Incorrect consumer offsets after broker restart 0.11.0.0

Thanks, we'll try upgrading to 0.11.0.1 and see if it fixes the problem. Is this the bug you are referring to? https://issues.apache.org/jira/browse/KAFKA-5600 -Original Message- From: Elyahou Ittah [mailto:elyaho...@fiverr.com] Sent: 10 October 2017 13:41 To: users@kafka.apache.org

Re: Incorrect consumer offsets after broker restart 0.11.0.0

It is a known bug, fixed in 0.11.0.1 On Oct 10, 2017 15:20, "Phil Luckhurst" wrote: > We have a Kafka broker we use for testing that we have recently updated > from 0.9.0.1 to 0.11.0.0 and our java consumer is built using the 0.11.0.0 > client. The consumers manually

kafka-streams dying if can't create internal topics

Hi all, still doing disaster testing with Kafka cluster, when crashing several brokers at once sometimes we observe exception in kafka-stream app about inability to create internal topics: [WARN ] [org.apache.kafka.streams.processor.internals.InternalTopicManager] [Could not create internal

Incorrect consumer offsets after broker restart 0.11.0.0

We have a Kafka broker we use for testing that we have recently updated from 0.9.0.1 to 0.11.0.0 and our java consumer is built using the 0.11.0.0 client. The consumers manually commit offsets and are consuming messages as expected since the upgrade. If we restart the consumers they fetch the

Re: NPE on ConsumerRecords$ConcatenatedIterable$1.makeNext() while iterating records

Can you please try with a newer version? Either 0.10.2.1 or 0.11.0.1? Ismael On Sun, Oct 8, 2017 at 2:29 PM, Michael Keinan wrote: > Hi > Using Kafka 0.10.2.0 > I get a NPE while iterating the records after polling them using poll > method. > - Any idea where does it

Re: Kafka Streams Transformer: context.forward() from different thread

Hi, No, context.forward() always needs to be called from the StreamThread. If you call it from another thread the behaviour is undefined and in most cases will be incorrect, likely resulting in an exception. On Tue, 10 Oct 2017 at 09:04 Murad Mamedov wrote: > Hi, here is the

Re: Consumer service that supports retry with exponential backoff

Hi John, It doesn't seem like you care for the ordering (since you're using multiple "fallback" topics that are processed in parallel if I understood you correctly), but the alternative would be to implement the backoff using the same topic and consumer. We're using the "pausing" feature of the

Re: NPE on ConsumerRecords$ConcatenatedIterable$1.makeNext() while iterating records

sign up for JIRA account and login to create an issue. On Tue, Oct 10, 2017 at 1:50 PM, Michael Keinan wrote: > Hi > So far I was unable to reproduce. I will try again. > The link you pasted gets me to the site but I can’t create an issue - how > can I do it ? > >

Re: NPE on ConsumerRecords$ConcatenatedIterable$1.makeNext() while iterating records

Hi So far I was unable to reproduce. I will try again. The link you pasted gets me to the site but I can’t create an issue - how can I do it ? Michael On Oct 9, 2017, at 12:38 PM, Manikumar > wrote: Hi, Can you reproduce the

Kafka Streams Transformer: context.forward() from different thread

Hi, here is the question: Transformer's transform() implementation starts some processing asynchronously, i.e. transform() implementation returns null. Then once asynchronous processing is complete in another thread, is it correct to call context.forward() from that thread? Thanks in advance