It's best to use "riak-admin ringready" between joins to make sure all nodes agree on the ring. It's possible that dev2 hadn't finished merging its ring with dev1's yet.
Sean Cribbs <[email protected]> Developer Advocate Basho Technologies, Inc. http://basho.com/ On Jan 17, 2011, at 8:39 AM, Jeremiah Peschka wrote: > +1 on what OJ is saying. > > The way you were first doing it is joining dev1 to a ring named > [email protected] and then attempting to join dev1 to a ring named [email protected] > > Jeremiah Peschka > Microsoft SQL Server MVP > MCITP: Database Developer, DBA > > > On Mon, Jan 17, 2011 at 7:00 AM, OJ Reeves <[email protected]> wrote: > I've always gone about it the other way: > > dev2/bin/riak-admin join dev1 > dev3/bin/riak-admin join dev1 > > Hasn't failed me yet :-) > > OJ > > Sent from my Windows Phone From: 吴磊 > Sent: Monday, 17 January 2011 8:46 PM > To: [email protected] > Subject: Joining running nodes should be in proper order? > When I join nodes like this: > dev1/bin/riak-admin join [email protected] > dev1/bin/riak-admin join [email protected] > > the ring has only 2 nodes: dev1 & dev2. I wait about 30 minutes, > nothing changed. > So I must join the ring nodes in some proper order? > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
