Currently, removing/leaving a node from a Riak cluster does not remove the node from the root ensemble. Thus, removed nodes look like offline/partitioned nodes and affect the ability of the root ensemble to meet quorum.
We need to fix this before shipping 2.0.
A related issue is that removing and rejoining a node of the same name is not safe -- even for non-root ensembles. This is because nothing is done to ensure old peer data is removed when leaving. Regardless of node name, the two instances of the same node should be considered logically disjoint peers with no shared history.
/cc basho/riak#536
Currently, removing/leaving a node from a Riak cluster does not remove the node from the root ensemble. Thus, removed nodes look like offline/partitioned nodes and affect the ability of the root ensemble to meet quorum.
We need to fix this before shipping 2.0.
A related issue is that removing and rejoining a node of the same name is not safe -- even for non-root ensembles. This is because nothing is done to ensure old peer data is removed when leaving. Regardless of node name, the two instances of the same node should be considered logically disjoint peers with no shared history.
/cc basho/riak#536