On Fri, Mar 1, 2013 at 7:08 AM, Ger Timmens <Ger.Timmens at adyen.com> wrote:
> All,
>
> When you do a drop node (e.g. node 19), there can still be records for
> that node in sl_confirm (both for con_received and con_origin.
> Shouldn't the drop node command just delete those records ?
>
> delete From _live_config.sl_confirm where con_received = 19;
> delete From _live_config.sl_confirm where con_origin = 19;

That logic is spread around a bit, and somewhat deferred.

See:
   function dropNode_int()
   function cleanupEvent()

The latter is the notable deferral; it's not desirable to drop the "entrails"
of node #19 immediately, as other nodes might still be working on
the last activity that had taken place on that node, so that the drop
mightn't take place "cleanly" if all the work takes place immediately.