What errors are you getting in your Zookeeper logs?
On Mon, Aug 11, 2014 at 7:54 PM, Andrew Xor <[email protected]> wrote: > Well, trident topologies compile directly to normal topologies. I think > you can get away with it albeit with a bit more code. > > > On Monday, August 11, 2014, Aaron Zimmerman <[email protected]> > wrote: > >> Just because I really like the api, I'm merging various data streams and >> then operating on them, storing each in a few places. It is a bit awkward >> to do in the usual spouts and bolts. >> >> >> On Mon, Aug 11, 2014 at 12:25 PM, Andrew Xor <[email protected] >> > wrote: >> >>> Why use a Trident topology then? Non transactional topologies have at >>> least once guarantee without the throughput pentalty imposed by using a >>> transactional topology. >>> >>> >>> On Monday, August 11, 2014, Aaron Zimmerman <[email protected]> >>> wrote: >>> >>>> Is it possible to use the trident API without having to track the >>>> transaction state in zookeeper? >>>> >>>> I have a high throughput topology, essentially ETL, and I don't need >>>> once and only once. The topology keeps dying, or tuples timeout, with >>>> zookeeper connection errors. I've raised the connection timeout to 25 >>>> seconds and the session timeout to 60 seconds and this hasn't seemed to >>>> help much. >>>> >>>> Thanks, >>>> >>>> Aaron Zimmerman >>>> >>> >>> >>> -- >>> Kindly yours, >>> >>> Andrew Grammenos >>> >>> -- PGP PKey -- >>> <https://www.dropbox.com/s/2kcxe59zsi9nrdt/pgpsig.txt> >>> https://www.dropbox.com/s/ei2nqsen641daei/pgpsig.txt >>> >>> >> > > -- > Kindly yours, > > Andrew Grammenos > > -- PGP PKey -- > <https://www.dropbox.com/s/2kcxe59zsi9nrdt/pgpsig.txt> > https://www.dropbox.com/s/ei2nqsen641daei/pgpsig.txt > > -- Danijel Schiavuzzi E: [email protected] W: www.schiavuzzi.com T: +385 98 9035562 Skype: danijel.schiavuzzi
