>
> 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
Seed node doesn’t bootstrap so if new node were to act as seed node, official
recommendations are to boot strap ‘new’ node first , only after that list that
node as seed.
Seed nodes are usually same across cluster nodes. You can designate 2 nodes as
seed per dc in order to mitigate network
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
>> r
>
> 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
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 h
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
the new node and an
already existing seed node and then start Cassandra?
What should I do? I am running nodetool nestats and the streaming are
happening from other nodes
Thanks
Il giorno gio 13 feb 2020 alle ore 17:39 Erick Ramirez <
erick.rami...@datastax.com> ha scritto:
> I wanted to
>
> 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
>This means that from the client driver perspective when I define the
contact points I can specify any node in the cluster as contact point and
not necessary a seed node?
Correct.
On Wed, Feb 12, 2020 at 11:48 AM Sergio wrote:
> So if
> 1) I stop the a Cassandra node that doe
Seed nodes are special in the sense that other nodes need them for
bootstrap (first startup only) and they have a special place in the Gossip
system. Odds of gossiping to a seed node are higher than other nodes, which
makes them "hubs" of gossip messaging.
Also, they do not boo
I define the
contact points I can specify any node in the cluster as contact point and
not necessary a seed node?
Best,
Sergio
On Wed, Feb 12, 2020, 9:08 AM Arvinder Dhillon
wrote:
> I believe seed nodes are not special nodes, it's just that you choose a
> few nodes from cluster that
I believe seed nodes are not special nodes, it's just that you choose a few
nodes from cluster that helps to bootstrap new joining nodes. You can
change Cassandra.yaml to make any other node as seed node. There's nothing
like promotion.
-Arvinder
On Wed, Feb 12, 2020, 8:37 AM Sergio wrote
Hi guys!
Is there a way to promote a not seed node to a seed node?
If yes, how do you do it?
Thanks!
d.
>
>
> *"Peng Xiao" <2535...@qq.com <2535...@qq.com>>*
>
> 03/28/2018 12:54 AM
> Please respond to
> user@cassandra.apache.org
>
> To
> "user" <user@cassandra.apache.org>,
>
> cc
> Subject
> Re: auto_bootstrap for seed
m>
03/28/2018 12:54 AM
Please respond to
user@cassandra.apache.org
To
"user" <user@cassandra.apache.org>,
cc
Subject
Re: auto_bootstrap for seed node
We followed this
https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_add_dc_to_cluster_t.html
,
but
t;<ali.hub...@petrolink.com>;
Date: Wed, Mar 28, 2018 10:48 AM
To: "user"<user@cassandra.apache.org>;
Subject: Re: auto_bootstrap for seed node
You might want to follow DataStax docs on this one:
For adding a DC to an existing cluster:
https://docs.datastax.com/en/dse/5
corded.
"Peng Xiao" <2535...@qq.com>
03/27/2018 09:39 PM
Please respond to
user@cassandra.apache.org
To
"user" <user@cassandra.apache.org>,
cc
Subject
auto_bootstrap for seed node
Dear All,
For adding a new DC ,we need to set auto_bootstrap: false and
Dear All,
For adding a new DC ,we need to set auto_bootstrap: false and then run the
rebuild,finally we need to change auto_bootstrap: true,but for seed nodes,it
seems that we still need to keep bootstrap false?
Could anyone please confirm?
Thanks,
Peng Xiao
> On Thu, Mar 22, 2018 at 5:04 PM, Nate McCall <n...@thelastpickle.com>
> wrote:
>
>> This capability was *just* added in CASSANDRA-14190 and only in trunk.
>>
>> Previously (as described in the ticket above), the seed node list is only
>> updated when doing a
> Previously (as described in the ticket above), the seed node list is only
> updated when doing a shadow round, removing an endpoint or restarting (look
> for callers of o.a.c.gms.Gossiper#buildSeedsList() if you're curious).
>
> A rolling restart is the usual SOP for that.
>
> On F
This capability was *just* added in CASSANDRA-14190 and only in trunk.
Previously (as described in the ticket above), the seed node list is only
updated when doing a shadow round, removing an endpoint or restarting (look
for callers of o.a.c.gms.Gossiper#buildSeedsList() if you're curious
We have a cluster that is subject to the one-year gossip bug.
We'd like to update the seed node list via JMX without restart, since our
foolishly single-seed-node in this forsaken cluster is being autoculled in
AWS.
Is this possible? It is not marked volatile in the Config of the source
code, so
into Reaper for past 2 months. Work in progress.
And thank you for the thorough response.
From: Alain RODRIGUEZ
Sent: Friday, March 2, 2018 11:43 AM
To: user cassandra.apache.org
Subject: Re: On a 12-node Cluster, Starting C* on a Seed Node Increases
ReadLatency from 150ms to 1.5 sec.
Hello
Hello,
This is a 2.8.8. cluster
That's an exotic version!
I understand you use Apache Cassandra 2.2.8. :)
This single node was a seed node and it was running a ‘repair -pr’ at the
> time
In Apache Cassandra 2.2.8, this triggers incremental repairs I believe, and
they are relatively (s
This is a 2.8.8. cluster with three AWS AZs, each with 4 nodes.
Few days ago we noticed a single node’s read latency reaching 1.5 secs there
was 8 others with read latencies going up near 900 ms.
This single node was a seed node and it was running a ‘repair -pr’ at the time.
We intervened
On Thu, Aug 3, 2017 at 3:00 PM, Fd Habash <fmhab...@gmail.com> wrote:
> Hi all …
>
> I know there is plenty of docs on how to replace a seed node, but some are
> steps are contradictory e.g. need to remote the node from seed list for
> entire cluster.
>
>
>
> My
Hi all …
I know there is plenty of docs on how to replace a seed node, but some are
steps are contradictory e.g. need to remote the node from seed list for entire
cluster.
My cluster has 6 nodes with 3 seeds running C* 2.8. One seed node was
terminated by AWS.
I came up with this procedure
No, any node can be seed node. But to start the cluster and nodes addition you
need some node as seed node. Make sure to include at least one node from each
DC as seed. DO NOT make all nodes as seed.
> On Jul 14, 2017, at 10:08 AM, Vikram Goyal G <vikram.g.go...@ericsson.com>
Hello,
Can you please comment if first node in a cluster must be a seed node. Is it
mandatory or not? How will it behave
Regards,
Vikram
Hi,
Is your OOM on heap or on native memory ? Since 2.1 put a lot of things on
native memory I would say that it is almost always bad to have 6 GB out of
8 for the heap (unless you have a very small data set), since in the 2 GB
remaining you have to keep bloom filters, indexes and more + Page
On Sat, Jun 13, 2015 at 4:39 AM, Oleksandr Petrov
oleksandr.pet...@gmail.com wrote:
We're using Cassandra, recently migrated to 2.1.6, and we're experiencing
constant OOMs in one of our clusters.
Maybe this memory leak?
https://issues.apache.org/jira/browse/CASSANDRA-9549
=Rob
The commitlog size is likely a red herring. In 2.0 we had 1gb commitlogs by
default. In 2.1 we have 8gb commitlogs by default. This is configurable at
the yaml.
Not sure what's causing the OOM. Did it generate an hprof file you can
analyze?
On Jun 13, 2015 7:42 AM, Oleksandr Petrov
Sorry I completely forgot to mention it in an original message: we have
rather large commitlog directory (which is usually rather small), 8G of
commitlogs. Draining and flushing didn't help.
On Sat, Jun 13, 2015 at 1:39 PM, Oleksandr Petrov
oleksandr.pet...@gmail.com wrote:
Hi,
We're using
Hi,
We're using Cassandra, recently migrated to 2.1.6, and we're experiencing
constant OOMs in one of our clusters.
It's a rather small cluster: 3 nodes, EC2 xlarge: 2CPUs, 8GB RAM, set up
with datastax AMI.
Configs (yaml and env.sh) are rather default: we've changed only concurrent
compactions
On Thu, Mar 19, 2015 at 3:56 PM, jean paul researche...@gmail.com wrote:
Please,i have a question a bout the seed node.. as i read it is the
bootstrap node, each new node joins the seed node that's it?
if it leaves the cluster, how can a new node joins the rest of the group ?
What a seed
Hello All,
Please,i have a question a bout the seed node.. as i read it is the
bootstrap node, each new node joins the seed node that's it?
if it leaves the cluster, how can a new node joins the rest of the group ?
Thanks a lot for answer.
Best Regards.
On Fri, Aug 29, 2014 at 7:09 PM, Donald Smith
donald.sm...@audiencescience.com wrote:
But the node is a seed node and cassandra won't bootstrap seed nodes.
Perhaps removing that node's address from the seeds list on the other nodes
(and on that node) will be sufficient. That's what Replacing
on
that node, (3) delete the data directory, (4) Use the tokens saved in step (1)
as the initial_token list, and (5) restart the node.
But the node is a seed node and cassandra won't bootstrap seed nodes. Perhaps
removing that node's address from the seeds list on the other nodes
Hi ,
I have a 4 node cassandra cluster with one node marked as seed node. When i
checked the data directory of seed node , it has two folders
/keyspace/columnfamily.
But sstable db files are not available.the folder is empty.The db files are
available in remaining nodes.
I want to know
of them should be on that seed
node.
- Node hasn't flushed yet.. You can use nodetool flush to try and flush
memtables manually.
- You're using manual token assignment and you didn't not assign them well.
On Mon, Feb 3, 2014 at 1:25 PM, Aravindan T aravinda...@tcs.com wrote:
Hi ,
I have a 4 node
' post below to say I don't believe we saw the message that
that slice of code would have printed.
Hey Rob,
Ed's AWOL right now and I'm not on u@c.a.o, but I can tell you that when
I removed the downed seed node from its own list of seed nodes in
cassandra.yaml that it didn't join
Hi
In our production, we have 3 Cassandra 1.0.11 nodes.
Due to a reason, I want to move the current seed node to another node and
once seed node change, the previous node want to remove from cluster.
How can I do that?
Thanks.
--
View this message in context:
http://cassandra-user
://www.thelastpickle.com
On 23/10/2012, at 7:13 PM, Roshan codeva...@gmail.com wrote:
Hi
In our production, we have 3 Cassandra 1.0.11 nodes.
Due to a reason, I want to move the current seed node to another node and
once seed node change, the previous node want to remove from cluster.
How can I do
can tell you that when
I removed the downed seed node from its own list of seed nodes in
cassandra.yaml that it didn't join the existing ring nor did it get any
schemas or data from the existing ring; it felt like timeouts were
happening. (IANA Cassandra wizard, so excuse my terminology
On Tue, Sep 11, 2012 at 4:21 PM, Edward Sargisson
edward.sargis...@globalrelay.net wrote:
If the downed node is a seed node then neither of the replace a dead node
procedures work (-Dcassandra.replace_token and taking initial_token-1). The
ring remains split.
[...]
In other words, if the host
How can this be resolved in this case?
On Wed, Sep 12, 2012 at 3:53 PM, Rob Coli rc...@palominodb.com wrote:
On Tue, Sep 11, 2012 at 4:21 PM, Edward Sargisson
edward.sargis...@globalrelay.net wrote:
If the downed node is a seed node then neither of the replace a dead node
procedures work
tell you that when
I removed the downed seed node from its own list of seed nodes in
cassandra.yaml that it didn't join the existing ring nor did it get any
schemas or data from the existing ring; it felt like timeouts were
happening. (IANA Cassandra wizard, so excuse my terminology impedance
Hi all,
We just ran into an interesting and unexpected situation with restarting
a downed node.
If the downed node is a seed node then neither of the replace a dead
node procedures work (-Dcassandra.replace_token and taking
initial_token-1). The ring remains split.
The host is listed
Boris Spasojevic boris.spasojevic at epfl.ch writes:
i have 2 machines , one windows and other linux. i am facing this issue. Could
you please tell me how you solved it.
Machine 1 OS listen_address thrift_address seeds JMX_PORT
server1Xp server1server1 server1
server2 should be pointing to server1 after server1 is online and in
the logs is accepting thrift connections. in what you've pasted
below, you show that server2 is connecting to server2 ... not server1.
-sd
On Tue, Apr 26, 2011 at 9:19 AM, Udit Khandelwal udi...@gmail.com wrote:
Boris
.
# Cassandra nodes use this list of hosts to find each other and learn
# the topology of the ring. You must change this if you are running
# multiple nodes!
seeds:
- 127.0.0.1
===
We don't want 127.0.0.1 to be used as the seed node. Our
!
seeds:
- 127.0.0.1
===
We don't want 127.0.0.1 to be used as the seed node. Our single node is
setup elsewhere right now.
Changing it in cassandra.yaml is not taking any immediate effect?
Even after changing it in cassandra.yaml
On Thu, Apr 21, 2011 at 9:10 PM, Nate McCall n...@datastax.com wrote:
Roshan,
See https://issues.apache.org/jira/browse/CASSANDRA-1777 for more details.
Hi...I am not sure I fully understand the current state of auto-discovery of
nodes.
The impression I am getting looking at the issue
It will work as long as thrift and gossip are bound to the same
interface. The discovery server in Hector also uses the
CassandraHostConfigurator#getPort for the port in constructing the
host URL.
On Thu, Apr 21, 2011 at 10:48 AM, Roshan Dawrani
roshandawr...@gmail.com wrote:
On Thu, Apr 21,
On Thu, Apr 21, 2011 at 9:30 PM, Nate McCall n...@datastax.com wrote:
It will work as long as thrift and gossip are bound to the same
interface. The discovery server in Hector also uses the
CassandraHostConfigurator#getPort for the port in constructing the
host URL.
Can you please elaborate
My seed node (1 of 4) having the wraparound range (token 0) needs to be
replaced.
Should I bootstrap the node with a new IP, then add it back as a seed?
Should I run remove token on another node to take over the range?
I shutdown cassandra, deleted (with a backup) the contents of the data
directory and did a nodetool move 0.It seems to be populating the node
with its range of data.Hope that was a good idea.
On Apr 11, 2011, at 10:38 PM, Jonathan Colby wrote:
My seed node (1 of 4) having
.Hope that was a good idea.
On Apr 11, 2011, at 10:38 PM, Jonathan Colby wrote:
My seed node (1 of 4) having the wraparound range (token 0) needs to be
replaced.
Should I bootstrap the node with a new IP, then add it back as a seed?
Should I run remove token on another node
Yes. This node has repeatedly given problems while reading various sstables.
So I decided to start with a fresh data dir, relying on the fact that with an
RF=3, the data will be able to be retrieved from the cluster.
Since this is a seed node, I am a little unsure how to proceed. From
, the problems happen:
1) new client connection cannot be established
sounds like pelops relies on the seed node to introduce it to the
cluster. you should configure it either with a hardcoded list of
nodes or use something like RRDNS instead. I don't use pelops so I
can't help other than that. (I
cluster: 3 machines (A, B, C)
details:
it works perfectly when all 3 machines are up and running
but if the seed machine is down, the problems happen:
1) new client connection cannot be established
sounds like pelops relies on the seed node to introduce it to the
cluster. you should
but if the seed machine is down, the problems happen:
1) new client connection cannot be established
sounds like pelops relies on the seed node to introduce it to the
cluster. you should configure it either with a hardcoded list of
nodes or use something like RRDNS instead. I don't use pelops
column family
list cf;
so i would like to know if the situation described above is normal or not?
if yes, does that mean the seed node is the single point of failure?
wing
Thanks all,
I have three questions:
1. Must seed list be identical on all nodes ?
2. If one seed node crash, all node will communication with the failure seed
node, I think this is harm for all nodes, isn't it？if this yes， how I can
replace the failure seed node in all node?
2010/12/8 Jonathan
. Must seed list be identical on all nodes ?2. If one seed node crash, all node will communication with the failure seed node, I think this is harm for all nodes, isn't it？if this yes， how I can replace the failure seed node in all node?
2010/12/8 Jonathan Ellis jbel...@gmail.com
"Two seed
You will need to restart the nodes for them to pickup changes in cassandra.yaml
Aaron
On 7 Dec 2010, at 16:32, lei liu wrote:
Thanks Nick.
After I add the new node as seed node in the configuration for all of my
nodes, do I need to restart all of my nodes?
2010/12/7 Nick Bailey n
Yes, cassandra only reads the configuration when it starts up. However seed
nodes are only used when a node starts. After that they aren't needed. There
should be no reason to restart your cluster after adding a seed node to
your cluster.
On Tue, Dec 7, 2010 at 2:09 AM, aaron morton aa
Note that there's not really anything special about the seed node and its
all relative– the cluster doesn't necessarily have to agreed on who the
seeds are.
So, to bring up a new node to replace the old seed, just set the new node's
seed to any existing node in the system. After that you can go
was a good idea. Obviously would not matter too much on a small cluster though.AaronOn 08 Dec, 2010,at 07:16 AM, Ryan King r...@twitter.com wrote:Note that there's not really anything special about the seed node and its all relative the cluster doesn't necessarily have to agreed on who the seeds
to gossip to one seed node.
Which made me think keeping the list sane and reasonably balanced was a
good idea. Obviously would not matter too much on a small cluster though.
Aaron
On 08 Dec, 2010,at 07:16 AM, Ryan King r...@twitter.com wrote:
Note that there's not really anything special
What would comprise a sane and reasonably balanced list? Should there be a
certain proportion of seeds per total nodes? Any other considerations
besides a) list must be identical on all nodes and b) you can't
auto-bootstrap a seed node?
I'm new to thinking about this setting, but it sounds like
-bootstrap a seed node?
Here's what we've used. No warranty beyond works for us
1) have more than 1 seed unless you can tolerate cluster outages
2) the the nodes should converge on agreement, but temporary discrepancies
in the seed lists on each node are acceptable
3) add seeds from pre-bootstrapped nodes
be identical on all nodes and b) you can't
auto-bootstrap a seed node?
I'm new to thinking about this setting, but it sounds like this discussion
may be approaching some best-practice guidelines.
On Tue, Dec 7, 2010 at 1:01 PM, Jonathan Ellis jbel...@gmail.com wrote:
The gossip-to-seed each round
After one seed node crash, I want to add one node as seed node, I set
*auto_bootstrap
to true, but the new node don't *migrate data from other nodes.
How can I add one new seed node and let the node to * *migrate data from
other nodes?
Thanks,
LiuLei
set it as a seed _after_ bootstrapping it into the cluster.
On Mon, Dec 6, 2010 at 5:01 AM, lei liu liulei...@gmail.com wrote:
After one seed node crash, I want to add one node as seed node, I set
auto_bootstrap to true, but the new node don't migrate data from other
nodes.
How can I add one
Thank Jonathan for your reply.
How can I bootstrap the node into cluster, I know if the node is seed node,
I can't set AutoBootstrap to true.
2010/12/6 Jonathan Ellis jbel...@gmail.com
set it as a seed _after_ bootstrapping it into the cluster.
On Mon, Dec 6, 2010 at t5:01 AM, lei liu
The node can be set as a seed node at any time. It does not need to be a
seed node when it joins the cluster. You should remove it as a seed node,
set autobootstrap to true and let it join the cluster. Once it has joined
the cluster you should add it as a seed node in the configuration for all
Thanks Nick.
After I add the new node as seed node in the configuration for all of my
nodes, do I need to restart all of my nodes?
2010/12/7 Nick Bailey n...@riptano.com
The node can be set as a seed node at any time. It does not need to be a
seed node when it joins the cluster. You should
Hi,
I am attempting to add a new node to a single node already running.
I have set the first node not to bootstrap, and the second node to
bootstrap whit the first node as it's seeder. The IP configuration is
OK, the machines can ping each other, the seed machine (or should I say
cassandra
Solved it!
Sorry to spam your inbox!
BoriS
On Fri, 2010-07-09 at 11:50 +0200, Boris Spasojevic wrote:
Hi,
I am attempting to add a new node to a single node already running.
I have set the first node not to bootstrap, and the second node to
bootstrap whit the first node as it's seeder.
Sounds like maybe your not binding the 7000 port to the correct interface,
maybe you have it set to localhost, rather then the IP address. If you want to
confirm, try prompt telnet [machine ip] 7000
If you get a connection refused, then the above is true.
Hope this helps.
Dimitry Lvovsky
90 matches
Mail list logo
