The current trigger design is simplistic and keeps all the intermediate state in memory. But this presents two problems when the overseer itself fails:
- We lose tracking state such as which node was added before the overseer restarted
- A nodeLost trigger can never really fire for the overseer node itself
So we need a way, preferably in the trigger API itself to save intermediate state or checkpoints so that it can seamlessly continue on overseer restarts.