On last question. Since this is a cluster there is only one public IP address. Doesn't that necessitate the ports being different values (ie 8088 -> node1, 8089 -> node2, 8090 -> node3 or something like that)?
-----Original Message----- From: Shane McEwan [mailto:[email protected]] Sent: Wednesday, December 12, 2012 10:12 AM To: Kevin Burton Cc: [email protected] Subject: Re: Cluster setup Looks good to me! On 12/12/12 16:10, Kevin Burton wrote: > 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% -- '[email protected]' > valid 34.4% -- '[email protected]' > valid 32.8% -- '[email protected]' > ---------------------------------------------------------------------- > ------ > --- > Valid:3 / Leaving:0 / Exiting:0 / Joining:0 / Down:0 > > Does this look right? > > > -----Original Message----- > From: Shane McEwan [mailto:[email protected]] > Sent: Wednesday, December 12, 2012 9:58 AM > To: Kevin Burton > Cc: [email protected] > 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 >> [email protected] <mailto:[email protected]>' 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 '[email protected]' >> >> --------------------------------------------------------------------- >> - >> --------- >> >> 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% '[email protected]' >> >> valid 100.0% 50.0% '[email protected]' >> >> --------------------------------------------------------------------- >> - >> --------- >> >> 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 '[email protected]' to '[email protected]' >> >> *I don't see [email protected] <mailto:[email protected]> in the >> cluster.* >> >> -----Original Message----- >> From: Shane McEwan [mailto:[email protected]] >> Sent: Wednesday, December 12, 2012 9:43 AM >> To: Kevin Burton >> Cc: [email protected] >> 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 [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
