Why does plumtree_per_service:leave/1 calls init:stop/0 after the node leaves the cluster ? Is it an arbitrary decision ? It looks a bit radical to me but I may have overlooked something.
Imagine the following use case : you have a running cluster, you need to do some operations on one node so you want to remove it from the cluster without shutting it down (so it does not loose its Gbs of cache/state/whatever). Leaving the cluster simply prevents you to do this and this might be quite a problem in some situations I think. It is up to the user to decide to leave the cluster and stop a node.
Hi there,
Why does
plumtree_per_service:leave/1callsinit:stop/0after the node leaves the cluster ? Is it an arbitrary decision ? It looks a bit radical to me but I may have overlooked something.Imagine the following use case : you have a running cluster, you need to do some operations on one node so you want to remove it from the cluster without shutting it down (so it does not loose its Gbs of cache/state/whatever). Leaving the cluster simply prevents you to do this and this might be quite a problem in some situations I think. It is up to the user to decide to leave the cluster and stop a node.