Mirror Maker [Aggregate cluster]

Hi there, I'm sorry about this silly question, just trying to make sure I got this right: Having a separate cluster for aggregate, means that I would need a second zookeeper for that cluster right? I would need a ZK for my local cluster, and then a ZK for my aggregate, is this correct? Regards

Topic stuck with leader: none

Hi there! So, I setup a demo and forgot to create the topic. But since my producer is set to create topics automatic, it created one. Problem is that after when sending messages I got a LeaderNotAvailableException. I ran topic-list shell, and noticed that my topic had leader:none. So I removed and

Re: OffsetResponse: protocol size error

orCode": 0, > "offsets": [ > 0 > ] > } > ], > "topicName": "myTopic" > } > ], > "responseSize": 31, > "correlation

Protocol:Offsetrespose

Hi there, from the docs: "Time: Used to ask for all messages before a certain time (ms). There are two special values. Specify -1 to receive the latest offset (this will only ever return one offset). Specify -2 to receive the earliest available offsets." But when I send -1 as an offsetrequest I g

OffsetResponse: protocol size error

Hi there, when issuing offsetrequests with this payload: { "requestMessage": { "API_KEY": 2, "replicaId": 0, "topics": [ { "topicName": "myTopic", "partitions": [ { "partitionId": 0,

Re: Stale TopicMetadata

is a bug. Could you file a jira? > > Thanks, > > Jun > > > On Wed, Jul 10, 2013 at 8:52 AM, Vinicius Carvalho < > viniciusccarva...@gmail.com> wrote: > > > Hi there. Once again, I don't think I could get the docs on another > topic. > > >

Stale TopicMetadata

Hi there. Once again, I don't think I could get the docs on another topic. So my nodejs client connects to the broker and the first thing it does is store the topic metadata: data received { "brokers": [ { "nodeId": 0, "host": "10.139.245.106", "por

Re: Network and partition

Thanks Jun On Wed, Jul 10, 2013 at 12:17 AM, Jun Rao wrote: > For 1, you will get a response with an error. > > For 2, a partition # has to be specified. If it is incorrect, you will get > a response with an error. > > Thanks, > > Jun > > > On Tue, Jul 9, 20

Network and partition

Hi there. I'm working on a 0.8 version of the protocol for nodejs. And when thing that I'm not clear from the docs: "The client will likely need to maintain a connection to multiple brokers, as data is partitioned and the clients will need to talk to the server that has their data" Ok, so far so

Re: 0.8 protocol exception

buffer, with the client I wrote, for clientId > "perl-kafka" and topics "foo" and "myTopic": > > 00 00 00 26 00 03 00 00 00 00 00 2a 00 0a 70 65 72 6c 2d 6b 61 66 6b 61 > 00 00 00 02 00 03 66 6f 6f 00 07 6d 79 54 6f 70 69 63 > > > On 07/08/2013 04

Re: 0.8 protocol exception

Ok, so I've found out the error: The documentation is outdated, the MetadataRequest BNF should be: NumberOfTopics [TopicList] Had to check the scala source code for that. Is there a place with a most to date doc? Regards On Mon, Jul 8, 2013 at 6:42 AM, Vinicius Carvalho < vinici

0.8 protocol exception

Hi there. I'm building the 0.8 version of a client to nodejs. I never coded for node and most of my code is following what the prozees guys did (I'm talking to them on updating the lib) But, I'm facing some errors when I test a very simple metadata request. I'm getting this exception on kafka: ja

Partitions and highlevel consumers

Hi guys, we are starting with kafka in our project. We are using version 0.8. I come from a traditional JMS MoM architecture, and some things are new to me. One thing that I'm not getting is the mapping between partitions and number of threads. On a single consumer I can see the relationship but w