Re: Restart App and consume from checkpoint using direct kafka API
I have implemented the above approach with cassandra db. Thank you all. On Thu, Mar 31, 2016 at 8:26 PM, Cody Koeningerwrote: > Long story short, no. Don't rely on checkpoints if you cant handle > reprocessing some of your data. > > On Thu, Mar 31, 2016 at 3:02 AM, Imre Nagi > wrote: > > I'm dont know how to read the data from the checkpoint. But AFAIK and > based > > on my experience, I think the best thing that you can do is storing the > > offset to a particular storage such as database everytime you consume the > > message. Then read the offset from the database everytime you want to > start > > reading the message. > > > > nb: This approach is also explained by Cody in his blog post. > > > > Thanks > > > > On Thu, Mar 31, 2016 at 2:14 PM, vimal dinakaran > > wrote: > >> > >> Hi, > >> In the blog > >> https://github.com/koeninger/kafka-exactly-once/blob/master/blogpost.md > >> > >> It is mentioned that enabling checkpoint works as long as the app jar is > >> unchanged. > >> > >> If I want to upgrade the jar with the latest code and consume from kafka > >> where it was stopped , how to do that ? > >> Is there a way to read the binary object of the checkpoint during init > and > >> use that to start from offset ? > >> > >> Thanks > >> Vimal > > > > >
Re: Restart App and consume from checkpoint using direct kafka API
Long story short, no. Don't rely on checkpoints if you cant handle reprocessing some of your data. On Thu, Mar 31, 2016 at 3:02 AM, Imre Nagiwrote: > I'm dont know how to read the data from the checkpoint. But AFAIK and based > on my experience, I think the best thing that you can do is storing the > offset to a particular storage such as database everytime you consume the > message. Then read the offset from the database everytime you want to start > reading the message. > > nb: This approach is also explained by Cody in his blog post. > > Thanks > > On Thu, Mar 31, 2016 at 2:14 PM, vimal dinakaran > wrote: >> >> Hi, >> In the blog >> https://github.com/koeninger/kafka-exactly-once/blob/master/blogpost.md >> >> It is mentioned that enabling checkpoint works as long as the app jar is >> unchanged. >> >> If I want to upgrade the jar with the latest code and consume from kafka >> where it was stopped , how to do that ? >> Is there a way to read the binary object of the checkpoint during init and >> use that to start from offset ? >> >> Thanks >> Vimal > > - To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
Re: Restart App and consume from checkpoint using direct kafka API
I'm dont know how to read the data from the checkpoint. But AFAIK and based on my experience, I think the best thing that you can do is storing the offset to a particular storage such as database everytime you consume the message. Then read the offset from the database everytime you want to start reading the message. nb: This approach is also explained by Cody in his blog post. Thanks On Thu, Mar 31, 2016 at 2:14 PM, vimal dinakaranwrote: > Hi, > In the blog > https://github.com/koeninger/kafka-exactly-once/blob/master/blogpost.md > > It is mentioned that enabling checkpoint works as long as the app jar is > unchanged. > > If I want to upgrade the jar with the latest code and consume from kafka > where it was stopped , how to do that ? > Is there a way to read the binary object of the checkpoint during init and > use that to start from offset ? > > Thanks > Vimal >
Restart App and consume from checkpoint using direct kafka API
Hi, In the blog https://github.com/koeninger/kafka-exactly-once/blob/master/blogpost.md It is mentioned that enabling checkpoint works as long as the app jar is unchanged. If I want to upgrade the jar with the latest code and consume from kafka where it was stopped , how to do that ? Is there a way to read the binary object of the checkpoint during init and use that to start from offset ? Thanks Vimal