You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
Why does
plumtree_per_service:leave/1
callsinit: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.
The text was updated successfully, but these errors were encountered: