>
> Just follow up to your statement:
> Limiting the seeds to 2 per DC means :
> A) Each node in a DC has at least 2 seeds and those seeds belong to the
> same DC
> or
> B) Each node in a DC has at least 2 seeds even across different DC
>
I apologise for the ambiguity of my previous response, I
in the cluster immediately UN without passing for UJ
state
Hi Erick!
Just follow up to your statement:
Limiting the seeds to 2 per DC means :
A) Each node in a DC has at least 2 seeds and those seeds belong to the same DC
or
B) Each node in a DC has at least 2 seeds even across different DC
Hi Erick!
Just follow up to your statement:
Limiting the seeds to 2 per DC means :
A) Each node in a DC has at least 2 seeds and those seeds belong to the
same DC
or
B) Each node in a DC has at least 2 seeds even across different DC
Thanks,
Sergio
Il giorno gio 13 feb 2020 alle ore 19:46
Not a problem. And I've just responded on the new thread. Cheers!
>
Thank you very much for this helpful information!
I opened a new thread for the other question :)
Sergio
Il giorno gio 13 feb 2020 alle ore 19:22 Erick Ramirez <
erick.rami...@datastax.com> ha scritto:
> I want to have more than one seed node in each DC, so unless I don't
>> restart the node
>
> I want to have more than one seed node in each DC, so unless I don't
> restart the node after changing the seed_list in that node it will not
> become the seed.
That's not really going to hurt you if you have other seeds in other DCs.
But if you're willing to take the hit from the restart
Right now yes I have one seed per DC.
I want to have more than one seed node in each DC, so unless I don't
restart the node after changing the seed_list in that node it will not
become the seed.
Do I need to update the seed_list across all the nodes even in separate DCs
and perform a rolling
>
> 1) If I don't restart the node after changing the seed list this will
> never become the seed and I would like to be sure that I don't find my self
> in a spot where I don't have seed nodes and this means that I can not add a
> node in the cluster
Are you saying you only have 1 seed node in
Thank you very much for your response!
2 things:
1) If I don't restart the node after changing the seed list this will never
become the seed and I would like to be sure that I don't find my self in a
spot where I don't have seed nodes and this means that I can not add a node
in the cluster
2)
>
> I did decommission of this node and I did all the steps mentioned except
> the -Dcassandra.replace_address and now it is streaming correctly!
That works too but I was trying to avoid the rebalance operations (like
streaming to restore replica counts) since they can be expensive.
So
I did decommission of this node and I did all the steps mentioned except
the -Dcassandra.replace_address and now it is streaming correctly!
So basically, if I want this new node as seed should I add its IP address
after it joined the cluster and after
- nodetool drain
- restart cassandra?
I
>
> Should I do something to fix it or leave as it?
It depends on what your intentions are. I would use the "replace" method to
build it correctly. At a high level:
- remove the IP from it's own seeds list
- delete the contents of data, commitlog and saved_caches
- add the replace flag in
Thanks for your fast reply!
No repairs are running!
https://cassandra.apache.org/doc/latest/faq/index.html#does-single-seed-mean-single-point-of-failure
I added the node IP itself and the IP of existing seeds and I started
Cassandra.
So the right procedure is not to add in the seed list the
>
> I wanted to add a new node in the cluster and it looks to be working fine
> but instead to wait for 2-3 hours data streaming like 100GB it immediately
> went to the UN (UP and NORMAL) state.
>
Are you running a repair? I can't see how it's possibly receiving 100GB
since it won't bootstrap.
Should I do something to fix it or leave as it?
On Thu, Feb 13, 2020, 5:29 PM Jon Haddad wrote:
> Seeds don't bootstrap, don't list new nodes as seeds.
>
> On Thu, Feb 13, 2020 at 5:23 PM Sergio wrote:
>
>> Hi guys!
>>
>> I don't know how but this is the first time that I see such behavior. I
Seeds don't bootstrap, don't list new nodes as seeds.
On Thu, Feb 13, 2020 at 5:23 PM Sergio wrote:
> Hi guys!
>
> I don't know how but this is the first time that I see such behavior. I
> wanted to add a new node in the cluster and it looks to be working fine but
> instead to wait for 2-3
Hi guys!
I don't know how but this is the first time that I see such behavior. I
wanted to add a new node in the cluster and it looks to be working fine but
instead to wait for 2-3 hours data streaming like 100GB it immediately went
to the UN (UP and NORMAL) state.
I saw a bunch of exception in
17 matches
Mail list logo
