In my use case, the chain is quite big and the time is unpredictable. Each tuple emitted by spout can emit about 100 tuples. And then those child tuples have to do REST calls which can take about 2-3 seconds. Then inserts, maintaining states, stateQuery, then again processings at the end again save to database.
1. The flow some what looks like this. In between I have eliminated lot more each blocks. How will guaranteed message processing exactly happens in this case? 2. Setting proper timeouts at spout level does not help as time taken to process a tuple is unpredicted and processing tuples multiple times is a costly operation - How to make sure that the storm does not re emits based on time? 3. How big can a normal topology or trident topology chain can be? Thanks Pratyusha
