Mar 29 03:39:16 ip-x.x.x.x.ec2.internal scylla[16615]: [shard 0] gossip - Gossip shadow round started with nodes={x.x.x.x,x.x.x.x,x.x.x.x,x.x.x.x,x.x.x.x}(all the seed nodes )
Mar 29 03:39:16 ip-x.x.x.x-ec2.internal scylla[16615]: [shard 0] rpc - client x.x.x.x:10145: fail to connect: Connection refused
--
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/029cbeaa-2511-4d22-8dd1-84ec6db0858bn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/CAO1GqFaFLYVN4W8N2JzHbivdKdjbVUyayjt3dXAB23ZEUMnLVQ%40mail.gmail.com.
so it should be the first node ip as seed ip in the entire cluster or in that DC, like in my case i have 3 DC so first DC is having 1 node as seed ip in the entire dc and so on correct me if i am wrong here or 1 seed ip in the entire cluster ?Also another question here if we want to replace the seed node (like normal process we used to remove that node ip from seed list and bootstraped it with replace address and auto_bootstrap option for streaming but in this case how to do that also what will happen if the seed node will down .Also according to this below documentation we have to add the other node ip in the seed list later ,please help me to understand this.
--On Mon, Mar 29, 2021 at 8:01 PM Asias He <as...@scylladb.com> wrote:--Hello Ishann,With the seedless feature, once the node is bootstrapped you can forget about the seed, no need to add 2 seeds per dc in the seed list. In your case, just use the ip of the first node bootstrapped as the seed (we now call it contact point) for the rest of the nodes. That's it.On Tue, Mar 30, 2021 at 2:49 AM Ishaan mohapatra <ishaan.moh...@gmail.com> wrote:Hi guys, I was trying to start a fresh Multi Data Centers cluster with 6 seed ip (2 in each dc ) (scylla version4.3) but nt able to start scylla service in the first seed node with this error
Mar 29 03:39:16 ip-x.x.x.x.ec2.internal scylla[16615]: [shard 0] gossip - Gossip shadow round started with nodes={x.x.x.x,x.x.x.x,x.x.x.x,x.x.x.x,x.x.x.x}(all the seed nodes )
Mar 29 03:39:16 ip-x.x.x.x-ec2.internal scylla[16615]: [shard 0] rpc - client x.x.x.x:10145: fail to connect: Connection refused
Mar 29 03:39:16 ip-x.x.x.x.ec2.internal scylla[16615]: [shard 0] gossip - Node x.x.x.x is down for get_endpoint_states verb [shard 0] gossip - Node x.x.x.x(one seed ip) is down for get_endpoint_states verb but after checking the scylla release note for 4.3 seedless concept and tried the node with only 1 seed(1st ip) node started without any issue so do we need to start all the other nodes in the cluster with 1 seed ip and add the other seed nodes once whole cluster is UN.https://www.scylladb.com/2020/09/22/seedless-nosql-getting-rid-of-seed-nodes-in-scylla/--Please help me here.
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/029cbeaa-2511-4d22-8dd1-84ec6db0858bn%40googlegroups.com.
--Asias
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/CAO1GqFaFLYVN4W8N2JzHbivdKdjbVUyayjt3dXAB23ZEUMnLVQ%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/CANZZLTiWHoDm%3Dq6zdQN_9tzmLns5fEmzb%3DduKpafFO7jbbL04g%40mail.gmail.com.