Hi Users, I successfully configured 2 Nodes Cluster , but when I configured 3rd Node and try to join them , then 3rd node is not able to join Cluster and I am getting below message. Please correct me in case of I am wrong at some place.
> WARN [GossipStage:1] 2017-11-07 17:01:42,706 TokenMetadata.java:215 - > Token -2625048720051242117 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,707 TokenMetadata.java:215 - > Token 2046352110807728035 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,708 TokenMetadata.java:215 - > Token 6738112847220178646 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,710 TokenMetadata.java:215 - > Token 5278402616817535783 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,710 TokenMetadata.java:215 - > Token -4301762166942209316 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,711 TokenMetadata.java:215 - > Token -5795150382485882189 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,711 TokenMetadata.java:215 - > Token -7650474240486110510 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,712 TokenMetadata.java:215 - > Token -7529017452803179703 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,713 TokenMetadata.java:215 - > Token -6321052415922186365 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,713 TokenMetadata.java:215 - > Token 505028918401730880 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,714 TokenMetadata.java:215 - > Token -6468981120406928540 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,714 TokenMetadata.java:215 - > Token -7886589494812723279 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,715 TokenMetadata.java:215 - > Token 6159957549175666279 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,715 TokenMetadata.java:215 - > Token 1371713730179023942 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,716 TokenMetadata.java:215 - > Token 3849374212689985831 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,717 TokenMetadata.java:215 - > Token -9130845474615238557 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,717 TokenMetadata.java:215 - > Token -2166821314373815731 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,718 TokenMetadata.java:215 - > Token 8172072992908340093 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,719 TokenMetadata.java:215 - > Token 5862934089465703397 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,719 TokenMetadata.java:215 - > Token 8683259820133858856 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,720 TokenMetadata.java:215 - > Token -6722468819050104438 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,720 TokenMetadata.java:215 - > Token 390606262920645821 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,721 TokenMetadata.java:215 - > Token -2191770340916232589 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,721 TokenMetadata.java:215 - > Token -2315498798364455538 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,722 TokenMetadata.java:215 - > Token -4289328221922359195 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,722 TokenMetadata.java:215 - > Token -3989195857321645521 changing ownership from /172.16.51.160 to / > 172.16.51.185 > WARN [GossipStage:1] 2017-11-07 17:01:42,723 TokenMetadata.java:215 - > Token -6852043742105779264 changing ownership from /172.16.51.160 to / > 172.16.51.185 Thanks and Best Regards, Nandan On Tue, Nov 7, 2017 at 12:48 PM, @Nandan@ <nandanpriyadarshi...@gmail.com> wrote: > Hi All, > > Thanks for sharing all information. > I am starting to work on this. > Now Problem which I am getting right now is:- > 1) How to select Network for Virtual Machine by which I can able to get > different IP for different Virtual Box? > 2) As I am using WIFI for HOST machine which is Windows 10, so is there > any internal configuration required or I need to select specific Network > Adapter into Virtual Boxs by which I will get IP1,IP2,IP3 for > node1,node2,node3 respectively. > > Please give me some ideas. > Thanks in advance, > Nandan Priyadarshi > > > On Tue, Nov 7, 2017 at 8:28 AM, James Briggs <james.bri...@yahoo.com. > invalid> wrote: > >> Nandan: The original Datastax training classes (when it was still called >> Riptano) >> used 3 virtualbox Debian instances to setup a Cassandra cluster. >> >> Thanks, James Briggs. >> -- >> Cassandra/MySQL DBA. Available in San Jose area or remote. >> cass_top: https://github.com/jamesbriggs/cassandra-top >> >> >> ------------------------------ >> *From:* kurt greaves <k...@instaclustr.com> >> *To:* User <user@cassandra.apache.org> >> *Sent:* Monday, November 6, 2017 3:08 PM >> *Subject:* Re: Reg :- Multiple Node Cluster set up in Virtual Box >> >> Worth keeping in mind that in 3.6 onwards nodes will not start unless >> they can contact a seed. Not quite SPOF but still problematic. >> CASSANDRA-13851 <https://issues.apache.org/jira/browse/CASSANDRA-13851> >> >> >> >
