At 2011-11-28T17:19+0000, Paul Armstrong wrote: > We have a 1.0.2 cluster with a node that's gone but still listed in > member_status (as legacy): > > riak-admin member_status > Attempting to restart script through sudo -u riak > ================================= Membership > ================================== > Status Ring Pending Node > ------------------------------------------------------------------------------- > (legacy) 7.8% -- '[email protected]' > valid 7.8% -- '[email protected]' > valid 7.8% -- '[email protected]' > valid 7.8% -- '[email protected]' > valid 7.8% -- '[email protected]' > valid 7.6% -- '[email protected]' > valid 7.6% -- '[email protected]' > valid 7.6% -- '[email protected]' > valid 7.6% -- '[email protected]' > valid 7.6% -- '[email protected]' > valid 7.6% -- '[email protected]' > valid 7.6% -- '[email protected]' > valid 7.6% -- '[email protected]' > ------------------------------------------------------------------------------- > Valid:13 / Leaving:0 / Exiting:0 / Joining:0 / Down:0
Many thanks to the Basho team (Dan Reverri and Mark Phillips in particular) for helping to solve this. The ring was corrupted and there was an interesting bug around legacy gossip and forced removal (see Bug 1298: Legacy gossip / force-remove troubles ---> https://issues.basho.com/show_bug.cgi?id=1298 ) After some erlang console work, our ring no longer had the ghost hosts in it, was able to settle into the new gossip mode and we were able to shrink it. Paul _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
