Hi I am using the kafka 0.7 and kafka spout from storm contrib. It is the ordinary storm spout and not the trident spout
On Wed, Feb 12, 2014 at 9:35 PM, Danijel Schiavuzzi <[email protected]>wrote: > Hi Chitra, > > Which Kafka spout version are you exactly using, and what spout type -- > Trident or the ordinary Storm spout? > > I ask that because, unfortunately, there are multiple Kafka spout versions > around the web. According to my research, your best bet is the one in > storm-contrib in case you use Kafka version 0.7, and storm-kafka-0.8-plus > in case you use Kafka 0.8. > > Best regards, > > Danijel Schiavuzzi > www.schiavuzzi.com > > > On Wed, Feb 12, 2014 at 8:42 AM, Chitra Raveendran < > [email protected]> wrote: > >> Hi >> >> I have a topology in production which uses the default kafka spout, I >> have set this parameter >> *spoutConfig.forceStartOffsetTime(-1);* >> >> This parameter -1 helps me in such a way that, it consumes from the >> latest message, and doesn't start reading data from kafka right from the >> beginning (That would be unnecessary and redundant in my usecase). >> >> But in production, whenever a new release goes in, I stop and start the >> topology which would take a few seconds to minutes. I have been loosing out >> on some data during the time that the topology is down. >> >> How can I avoid this. I have tried running without the ForcedOffsetTime >> parameter, but that did not work. What am I doing wrong, how can I continue >> reading from the last offest ? >> >> Thanks, >> Chitra >> >> > > > -- > Danijel Schiavuzzi > -- Regards, *Chitra Raveendran* *Data Scientist* Mobile: +91 819753660│*Email:* [email protected] *Flutura Business Solutions Private Limited – “A Decision Sciences & Analytics Company”*│ #693, 2nd Floor, Geetanjali, 15th Cross, J.P Nagar 2nd Phase, Bangalore – 560078│
