So now I have [azureuser@bsicentos3 ~]$ sudo riak-admin member-status Attempting to restart script through sudo -H -u riak ================================= Membership ================================== Status Ring Pending Node ---------------------------------------------------------------------------- --- valid 32.8% -- 'riak@10.79.108.25' valid 34.4% -- 'riak@10.79.110.52' valid 32.8% -- 'riak@10.79.90.11' ---------------------------------------------------------------------------- --- Valid:3 / Leaving:0 / Exiting:0 / Joining:0 / Down:0
Does this look right? -----Original Message----- From: Shane McEwan [mailto:sh...@mcewan.id.au] Sent: Wednesday, December 12, 2012 9:58 AM To: Kevin Burton Cc: riak-users@lists.basho.com Subject: Re: Cluster setup Run the join commands on the OTHER machines . . . NOT the master. Use the master's IP address in the join commands but the actual command must be run on the non-master machines. You're telling the "slave" machines to join the cluster by telling them which machine they need to talk to to get the cluster information. On 12/12/12 15:51, Kevin Burton wrote: > *So again from the master I do 'sudo riak-admin cluster join > riak@10.79.90.11 <mailto:riak@10.79.90.11>' but I get:* > > [sudo] password for azureuser: > > Attempting to restart script through sudo -H -u riak > > Failed: This node is already a member of a cluster > > *Looking at the plan:* > > [azureuser@bsicentos1 ~]$ sudo riak-admin cluster plan > > Attempting to restart script through sudo -H -u riak > > =============================== Staged Changes > ================================ > > Action Nodes(s) > > ---------------------------------------------------------------------- > --------- > > join 'riak@10.79.108.25' > > ---------------------------------------------------------------------- > --------- > > NOTE: Applying these changes will result in 1 cluster transition > > ###################################################################### > ######### > > After cluster transition 1/1 > > ###################################################################### > ######### > > ================================= Membership > ================================== > > Status Ring Pending Node > > ---------------------------------------------------------------------- > --------- > > valid 0.0% 50.0% 'riak@10.79.108.25' > > valid 100.0% 50.0% 'riak@10.79.110.52' > > ---------------------------------------------------------------------- > --------- > > Valid:2 / Leaving:0 / Exiting:0 / Joining:0 / Down:0 > > WARNING: Not all replicas will be on distinct nodes > > Transfers resulting from cluster changes: 32 > > 32 transfers from 'riak@10.79.110.52' to 'riak@10.79.108.25' > > *I don't see riak@10.79.90.11 <mailto:riak@10.79.90.11> in the > cluster.* > > -----Original Message----- > From: Shane McEwan [mailto:sh...@mcewan.id.au] > Sent: Wednesday, December 12, 2012 9:43 AM > To: Kevin Burton > Cc: riak-users@lists.basho.com > Subject: Re: Cluster setup > > There's no need to join the "master" to itself. Just join the other > nodes to the master. > _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
