Although I don't have extensive knowledge in kafkaspout, I have always thought that if you have same customerID in the same zookeeper, it will read from same node in zookeeper, thus one topology reading a message will update the offset for the both topologies.. I might be wrong tho.
*Seungtack Baek | Precocity, LLC* Tel/Direct: (972) 378-1030 | Mobile: (214) 477-5715 *[email protected] <[email protected]>* | www.precocityllc.com This is the end of this message. -- On Mon, Jun 22, 2015 at 8:13 PM, 이승진 <[email protected]> wrote: > This will duplicate messages to different topologies, though. > > > > Two same topologies with different id reading same topic in alternating > manner, it's pretty same to what Kafka's consumer group API behaves. > > > > -----Original Message----- > *From:* "Andrey Yegorov"<[email protected]> > *To:* <[email protected]>; "이승진"<[email protected]>; > *Cc:* > *Sent:* 2015-06-23 (화) 00:52:00 > *Subject:* Re: storm-kafka, consumer group support? > > > On Mon, Jun 22, 2015 at 2:47 AM, 이승진 <[email protected]> wrote: > > I think it's not possible currently, if this is the case, wouldn't it be > valuable if we support this? > > > SpoutConfig constructor has a parameter called IIRC "id" to identify > different clients for the same topic. > Just use different ids for different topologies. > > ---------- > Andrey Yegorov >
