In my personal experience, I could say like try to upgrade for latest
version. Because I could see stability issues like disruptor queue fills up
and storm getting hung in 0.9.4 version. I am in the upgrade process now
migrating from 0.9.4 to 1.2.1
On Tue, Mar 13, 2018, 2:05 AM Shubham Gupta
Thanks a lot
Regards
Shubham Gupta
On Mon, Mar 12, 2018 at 1:33 PM, Stig Rohde Døssing wrote:
> I'm basing this off of later Storm versions, because I'm not familiar with
> 0.9, so buyer beware. As far as I know the logic hasn't changed though, so
> I'll be linking to the
I'm basing this off of later Storm versions, because I'm not familiar with
0.9, so buyer beware. As far as I know the logic hasn't changed though, so
I'll be linking to the 2.0.0 classes.
1. No, you don't need to ack or fail unanchored tuples. Storm isn't keeping
track of those tuples at all.
Hi,
I had a few doubts regarding storm reliability mechanism :
- Do we need to ack (or fail) unanchored tuples ?
- Is is always necessary to ack or fail every tuple received from the spout
in the first bolt to avoid Out of Memory error in Storm ?
Thanks in advance
Regards
Shubham Gupta