Question: What is the expected behavior for re-registration with smaller I/O count before the garbage collect interval?

[isaacgr]

If a node dies and revives itself with a smaller I/O count within the garbage collect interval, and does not remember what it registered before it died (something I imagine it could use to delete its resources on startup) then what is the expected behavior?

What I'm seeing is that all the previous resources will remain in the registry. Since technically they never needed to get cleaned up as the node keepalive was never down long enough.

[garethsb]

If the Node doesn't remember its previous state, it should treat finding itself in the Registry as unexpected and delete the Node resource, which will cause the Registry to remove all the subresources, before beginning the registration of all its current new resources starting with the Node again. See https://github.com/AMWA-TV/is-04/blob/v1.3.x/docs/Behaviour%20-%20Registration.md#node-encounters-http-200-on-first-registration

[isaacgr]

If the Node doesn't remember its previous state, it should treat finding itself in the Registry as unexpected and delete the Node resource, which will cause the Registry to remove all the subresources, before beginning the registration of all its current new resources starting with the Node again. See https://github.com/AMWA-TV/is-04/blob/v1.3.x/docs/Behaviour%20-%20Registration.md#node-encounters-http-200-on-first-registration

Thanks!