Re: Does kafka version 0.9.0x use zookeeper?

Thanks Gerad On 4 April 2016 at 15:49, Gerard Klijs wrote: > Yes, but only via the broker you connect to. > > On Mon, Apr 4, 2016, 07:10 Ratha v wrote: > > > I'm not seeing such parameter as an input for consumer. > > > > Does version 0.9.x use

Re: New consumer API waits indefinitely

I too face same issue:( On 4 April 2016 at 15:51, Lohith Samaga M wrote: > HI, > Good morning. > > I am new to Kafka. So, please bear with me. > I am using the new Producer and Consumer API with Kafka > 0.9.0.1 running

New consumer API waits indefinitely

HI, Good morning. I am new to Kafka. So, please bear with me. I am using the new Producer and Consumer API with Kafka 0.9.0.1 running on Windows 7 laptop with zookeeper. I was able to send messages using the new Producer API. I can

Re: Does kafka version 0.9.0x use zookeeper?

Yes, but only via the broker you connect to. On Mon, Apr 4, 2016, 07:10 Ratha v wrote: > I'm not seeing such parameter as an input for consumer. > > Does version 0.9.x use zookeeper? > > -- > -Ratha > http://vvratha.blogspot.com/ >

Re: Kafka Streams: context.forward() with downstream name

2016-04-04 7:20 GMT+09:00 Guozhang Wang : > Hi Yuto, > > Is the destination topic embedded as part of the value in the original > "foo" topic? If yes could you just access that field directly instead of > mapping to a (key, value, destination) triplet? > Nope.

Does kafka version 0.9.0x use zookeeper?

I'm not seeing such parameter as an input for consumer. Does version 0.9.x use zookeeper? -- -Ratha http://vvratha.blogspot.com/

If my producer producing, then why the consumer couldn't consume? it stuck @ poll()

Hi all; Im publishing to the remote kafka server and try to consume messages from that remote server. (Kafka v 0.90.1) Publishing works fine but nor the consuming. *Publisher* package org.test; *import java.io.IOException;* *import java.util.Properties;* *import

Re: ProducerConfig - The configuration serializer.class = org.apache.kafka.common.serialization.StringSerializer was supplied but isn't a known config

Sorry my bad..my kafka docker instance was down.. thanks On 4 April 2016 at 10:09, Ratha v wrote: > > Hi all; > I'm getting above exception when i try to produce simple string messages > using kafka 0.9.01 version. I could not produce messages now. > > The warning i get

Re: About AMQP connector and Kafka Connect framework

On Fri, Apr 1, 2016 at 12:23 AM, Paolo Patierno wrote: > Hi Ewen, > > thanks for your reply. > > My objective here is to access Kafka through AMQP protocol (now I'm > working on a bridge from scratch without using Kafka Connect). > > Consider the following scenario ... > >

ProducerConfig - The configuration serializer.class = org.apache.kafka.common.serialization.StringSerializer was supplied but isn't a known config

Hi all; I'm getting above exception when i try to produce simple string messages using kafka 0.9.01 version. I could not produce messages now. The warning i get is; buffer.memory = 33554432 timeout.ms = 3 key.serializer = class org.apache.kafka.common.serialization.StringSerializer

Re: Kafka performance issue

Hey Tony, Are you connecting to Remote machine for Consumer and Producer? If yes try to check the network bandwidth. Do check the cluster configuration, memory, cpu resources, topic partitions, replication factor, you would get some trace. Thanks! VM On Apr 4, 2016 5:09 AM, "LeiNing"

Kafka performance issue

Hi guys, Hope you are doing well. I'm encountering a performance issue and would be highly appreciate if you can shed some light. There is no problem by only running producer or consumer, but when I run both of them at the same time, the performance is getting very slow. What

Re: Kafka constant shrinking and expanding after deleting a topic

Yifan, Are you on 0.8.0 or 0.8.1/2? There are some issues with zkVersion checking in 0.8.0 that are fixed in later minor releases of 0.8. Guozhang On Fri, Apr 1, 2016 at 7:46 PM, Yifan Ying wrote: > Hi All, > > We deleted a deprecated topic on Kafka cluster(0.8) and

Re: Upgrade path to 0.10.x

There are some discussions in maintaining client compatibility across broker versions, where the main idea is to allow clients to retrieve the broker version programmatically (details in KIP-35). As for now although clients and servers are released together they each can be treated as different

Re: Kafka Streams: context.forward() with downstream name

Hi Guozhang, 2016-04-02 3:29 GMT+09:00 Guozhang Wang : > Hi Yuto, > > That is a good suggestion, the child index is not very intuitive from > programmer's view and we can even consider replacing it with the processor > name instead of overloading it. Could you file a JIRA? >

Re: Upgrade path to 0.10.x

Hi Tommy, I think it's reasonable to think it should work. However, our upgrade tests don't currently test that scenario and that is why we only mention {0.8.2.x, 0.9.0.x} to 0.10.0.0: https://github.com/apache/kafka/blob/trunk/tests/kafkatest/tests/upgrade_test.py#L62 The best way to verify

Re: Upgrade path to 0.10.x

- This type of questions is pretty common on the ml. Personally I don't think I could confidently described the compatibility/upgrade scenarios. Some clarification is needed, ideally in a single place. I think this is even more crucial as the number of new features increases (which is exciting)