I am trying to understand the Spout restart scenario in relation to the acker.
If a topology relies on storm acker's tracking, what happens when a Spout task dies due to worker crash and gets restarted by the Supervisor? When the acker is about to notify the Spout on ack() or fail() it invokes emitDirect on the outputCollector. If a Spout task is unavailable, what happens to the notification? Thank you. This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
