Hello all - I have a simple topology where there is a fieldsGrouping on a bolt and it has an internal accumulator, so simply,
BoltA -> BoltB.fieldsGrouping( BoltA, "string for grouping" ) I never had a problem with this code before, it worked perfectly until the timeframe between accumulator emits exceeded an hour. What I came back to today was the topology had frozen for one of the groups, because the accumulator had restarted from one, which I thought should have been impossible. Basically I use a Map internally the key being the 'string for grouping' above and storing an integer object as the accumulator. When accumulator >= threshold, it emits a single message. So my question is, after reading much about how this could possibly happen: How does storm decide to 'retire' or 'kill' a bolt, that for all intents and purposes is working fine, but has not emitted in a long period? Is there a timeout configuration for that or some other regular behavior? The standard set size in production is going to take hour(s) before the accumulator hits the threshold and emits to the next stage of processing. Thanks! Rich
