RE: Seed List

, using ansible to add ‘new’ nodes to the ring: DC1, nodes 1-12 DC2 nodes 1-10 My first seed node was DC1, node 3 but ansible operated in numerical order. Thus, my cluster started with two nodes (DC1 node 1, node 2) which had no idea of one another until DC1 node 3 appeared. When I checked with

Re: Seed List

From my understanding, the main thing to be aware of is that Cassandra’s default SeedProvider doesn't resolve multiple A records, so you’re actually limited in terms of the load balancing/DNS configurations you can use. You can however write alternative seed providers which have diff

RE: Seed List

al Message- From: Marc Hoppins Sent: Thursday, June 23, 2022 3:33 AM To: user@cassandra.apache.org Subject: [EXTERNAL] Seed List Hi guys, Documentation (for almost everything) uses IP addresses for seeds, is it possible to use the FQDN instead for the seeds (cass.yaml)? It is far easier t

Seed List

Hi guys, Documentation (for almost everything) uses IP addresses for seeds, is it possible to use the FQDN instead for the seeds (cass.yaml)? It is far easier to read/use names. Thanks M

Re: cassandra-external-file-seed-provider: manage your list of seeds via an external file

Amazing, thank you so much. On Fri, Jun 25, 2021, 18:42 Jonathan Ballet wrote: > Hello, > > I wanted to announce a small project that I've worked on a while ago, that > may be useful to other people: > > https://github.com/multani/cassandra-external-file-seed-provider &g

cassandra-external-file-seed-provider: manage your list of seeds via an external file

Hello, I wanted to announce a small project that I've worked on a while ago, that may be useful to other people: https://github.com/multani/cassandra-external-file-seed-provider This is a simple seed provider that fetches the list of seeds from an externally managed file. The original goa

Re: Can you change seed nodes without doing a restart?

You just need to remove the node from it's own seeds list so it can bootstrap itself back into the cluster. Otherwise, it will immediately join the cluster without streaming data from other replicas. If you intend to promote it back as a seed node, you don't need to remove it from the

Can you change seed nodes without doing a restart?

Hi - when replacing a dead seed node, we need to make it not a seed node before replacing it. To do that, you need to change the cassandra.yaml values and (I believe) perform a rolling restart. Is the restart necessary? Thanks

Re: New seed node in the cluster immediately UN without passing for UJ state

> > 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 se

RE: New seed node in the cluster immediately UN without passing for UJ state

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

Re: New seed node 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 Thanks, Sergio Il giorno gio 13 feb 2020 alle ore 19:46 Er

Re: New seed node in the cluster immediately UN without passing for UJ state

Not a problem. And I've just responded on the new thread. Cheers! 👍 >

Re: New seed node in the cluster immediately UN without passing for UJ state

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 >&

Re: New seed node in the cluster immediately UN without passing for UJ state

> > 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 ta

Re: New seed node in the cluster immediately UN without passing for UJ state

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 ro

Re: New seed node in the cluster immediately UN without passing for UJ state

> > 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 sayin

Re: New seed node in the cluster immediately UN without passing for UJ state

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

Re: New seed node in the cluster immediately UN without passing for UJ state

sive. 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? There's no need to restart C* after updating the seeds list. It will just take effect the next time you restart. I deacti

Re: New seed node in the cluster immediately UN without passing for UJ state

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

Re: New seed node in the cluster immediately UN without passing for UJ state

> > 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 cassand

Re: New seed node in the cluster immediately UN without passing for UJ state

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

Re: New seed node in the cluster immediately UN without passing for UJ state

> > 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.

Re: New seed node in the cluster immediately UN without passing for UJ state

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 >

Re: New seed node in the cluster immediately UN without passing for UJ state

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 hours

New seed node in the cluster immediately UN without passing for UJ state

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 t

Re: How to elect a normal node to a seed node

>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 doesn'

Re: How to elect a normal node to a seed node

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 bootstra

Re: How to elect a normal node to a seed node

So if 1) I stop the a Cassandra node that doesn't have in the seeds IP list itself 2) I change the cassandra.yaml of this node and I add it to the seed list 3) I restart the node It will work completely fine and this is not even necessary. This means that from the client driver perspective

Re: How to elect a normal node to a seed node

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 Ser

How to elect a normal node to a seed node

Hi guys! Is there a way to promote a not seed node to a seed node? If yes, how do you do it? Thanks!

Re: How seed nodes are working and how to upgrade/replace them?

On Tue, 8 Jan 2019 at 18:29, Jeff Jirsa wrote: > Given Consul's popularity, seems like someone could make an argument that > we should be shipping a consul-aware seed provider. > Elasticsearch has a very handy dedicated file-based discovery system: https://www.elastic.co/guide/en

Re: How seed nodes are working and how to upgrade/replace them?

jira/browse/CASSANDRA-3829 which was very >> instructive, although a bit old. >> >> >> On Mon, 7 Jan 2019 at 17:23, Jeff Jirsa wrote: >> >>> > On Jan 7, 2019, at 6:37 AM, Jonathan Ballet >>> wrote: >>> > >>> [...] >>> >>

Re: How seed nodes are working and how to upgrade/replace them?

000 nodes, it's not even worth bothering with. Just be sure you have seeds in each DC. Something to be aware of - there's only a chance to gossip with a seed. That chance goes down as cluster size increases, meaning seeds have less and less of an impact as the cluster grows. Once you g

Re: How seed nodes are working and how to upgrade/replace them?

> On Mon, 7 Jan 2019 at 17:23, Jeff Jirsa wrote: > >> > On Jan 7, 2019, at 6:37 AM, Jonathan Ballet wrote: >> > >> [...] >> >> > In essence, in my example that would be: >> > >> > - decide that #2 and #3 will be the new seed nodes

Re: How seed nodes are working and how to upgrade/replace them?

Given Consul's popularity, seems like someone could make an argument that we should be shipping a consul-aware seed provider. On Tue, Jan 8, 2019 at 7:39 AM Jonathan Ballet wrote: > On Mon, 7 Jan 2019 at 16:51, Oleksandr Shulgin < > oleksandr.shul...@zalando.de> wrote: > &g

Re: How seed nodes are working and how to upgrade/replace them?

onathan Ballet wrote: > > > [...] > > > In essence, in my example that would be: > > > > - decide that #2 and #3 will be the new seed nodes > > - update all the configuration files of all the nodes to write the IP > addresses of #2 and #3 > > -

Re: How seed nodes are working and how to upgrade/replace them?

;> What I would like to do is to replace the machines holding our current >> seeds (#1 and #2 at the moment) in a rolling upgrade fashion, on a regular >> basis: >> >> * Is it possible to "promote" any non-seed node as a seed node? >> >> * Is it possible

Re: How seed nodes are working and how to upgrade/replace them?

> On Jan 7, 2019, at 8:23 AM, Jeff Jirsa wrote: > > > > >> On Jan 7, 2019, at 6:37 AM, Jonathan Ballet wrote: >> >> Hi, >> >> I'm trying to understand how seed nodes are working, when and how do they >> play a part in

Re: How seed nodes are working and how to upgrade/replace them?

> On Jan 7, 2019, at 6:37 AM, Jonathan Ballet wrote: > > Hi, > > I'm trying to understand how seed nodes are working, when and how do they > play a part in a Cassandra cluster, and how they should be managed and > propagated to other nodes. > > I hav

Re: How seed nodes are working and how to upgrade/replace them?

ds (#1 and #2 at the moment) in a rolling upgrade fashion, on a regular > basis: > > * Is it possible to "promote" any non-seed node as a seed node? > > * Is it possible to "promote" a new seed node without having to restart > all the nodes? > In essence, in

How seed nodes are working and how to upgrade/replace them?

Hi, I'm trying to understand how seed nodes are working, when and how do they play a part in a Cassandra cluster, and how they should be managed and propagated to other nodes. I have a cluster of 6 Cassandra nodes (let's call them #1 to #6), on which node #1 and #2 are seed

Re: auto_bootstrap for seed node

Setting auto_bootstrap on seed nodes is unnecessary and irrelevant. If the node is a seed it will ignore auto_bootstrap and it *will not* bootstrap. On 28 March 2018 at 15:49, Ali Hubail wrote: > "it seems that we still need to keep bootstrap false?" > > Could you shed some

Re: auto_bootstrap for seed node

"it seems that we still need to keep bootstrap false?" Could you shed some light on what would happen if the auto_bootstrap is removed (or set to true as the default value) in the seed nodes of the newly added DC? What do you have in the seeds param of the new DC nodes (cassandra.

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 it does not mention that change bootstrap for seed nodes after the rebuild. Thanks, Peng Xiao -- Original -- From: "Ali Hubail";

Re: auto_bootstrap for seed node

e recorded. "Peng Xiao" <2535...@qq.com> 03/27/2018 09:39 PM Please respond to user@cassandra.apache.org To "user" , cc Subject auto_bootstrap for seed node Dear All, For adding a new DC ,we need to set auto_bootstrap: false and then run the rebuild,fin

auto_bootstrap for seed node

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

Re: cassl 2.1.x seed node update via JMX

r 22, 2018 at 5:04 PM, Nate McCall > 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 shadow round, removing an endpoint or restart

Re: cassl 2.1.x seed node update via JMX

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 Fri, Mar 23, 2

Re: cassl 2.1.x seed node update via JMX

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

cassl 2.1.x seed node update via JMX

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 cod

Re: Seed nodes of DC2 creating own versions of system keyspaces

of "why". :) Is this again because of the very first seed node corner case? Will it hang indefinitely waiting for schema from other nodes if it would try? -- Alex

Re: Seed nodes of DC2 creating own versions of system keyspaces

;Jeff Jirsa" wrote: > > On Mar 5, 2018, at 6:40 AM, Oleksandr Shulgin < > oleksandr.shul...@zalando.de> wrote: > > We were deploying a second DC today with 3 seed nodes (30 nodes in total) > and we have noticed that all seed nodes reported the following: > > I

Re: Seed nodes of DC2 creating own versions of system keyspaces

On 6 Mar 2018 16:55, "Jeff Jirsa" wrote: On Mar 6, 2018, at 12:32 AM, Oleksandr Shulgin wrote: On 5 Mar 2018 16:13, "Jeff Jirsa" wrote: On Mar 5, 2018, at 6:40 AM, Oleksandr Shulgin wrote: We were deploying a second DC today with 3 seed nodes (30 nodes in total) and

Re: Seed nodes of DC2 creating own versions of system keyspaces

-- Jeff Jirsa > On Mar 6, 2018, at 12:32 AM, Oleksandr Shulgin > wrote: > > On 5 Mar 2018 16:13, "Jeff Jirsa" wrote: >> On Mar 5, 2018, at 6:40 AM, Oleksandr Shulgin >> wrote: >> We were deploying a second DC today with 3 seed nodes (30 nodes in

Re: Seed nodes of DC2 creating own versions of system keyspaces

On 5 Mar 2018 16:13, "Jeff Jirsa" wrote: On Mar 5, 2018, at 6:40 AM, Oleksandr Shulgin wrote: We were deploying a second DC today with 3 seed nodes (30 nodes in total) and we have noticed that all seed nodes reported the following: INFO 10:20:50 Create new Keyspace: KeyspaceMet

Re: Seed nodes of DC2 creating own versions of system keyspaces

> On Mar 5, 2018, at 6:40 AM, Oleksandr Shulgin > wrote: > > Hi, > > We were deploying a second DC today with 3 seed nodes (30 nodes in total) and > we have noticed that all seed nodes reported the following: > > INFO 10:20:50 Create new Keyspace: Keyspace

Seed nodes of DC2 creating own versions of system keyspaces

Hi, We were deploying a second DC today with 3 seed nodes (30 nodes in total) and we have noticed that all seed nodes reported the following: INFO 10:20:50 Create new Keyspace: KeyspaceMetadata{name=system_traces, params=KeyspaceParams{durable_writes=true, replication=ReplicationParams{class

RE: On a 12-node Cluster, Starting C* on a Seed Node Increases ReadLatency from 150ms to 1.5 sec.

from its seed provider list. Otherwise, it won’t bootstrap. . You should be able to have nodes going down, or being fairly slow … - When we stopped C* on this node, read performance recovered well. Once started, and now with no repairs running at all, latency increased bad to over 1.5 secs. This

Re: On a 12-node Cluster, Starting C* on a Seed Node Increases Read Latency from 150ms to 1.5 sec.

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 relative

On a 12-node Cluster, Starting C* on a Seed Node Increases Read Latency from 150ms to 1.5 sec.

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 as

Re: Seed nodes and bootstrap (was: Re: Initializing a multiple node cluster (multiple datacenters))

On Mon, Feb 26, 2018 at 7:05 PM, Jeff Jirsa wrote: > > I'll happily click the re-open button (you could have, too), but I'm not > sure what the 'right' fix is. Feel free to move discussion to 5836. > Thanks, Jeff. Somehow, I don't see any control elements to change issue status, even though I'

Re: Seed nodes and bootstrap (was: Re: Initializing a multiple node cluster (multiple datacenters))

n Fri, Feb 23, 2018 at 7:35 PM, Jeff Jirsa wrote: > >> It comes up from time to time. Rob Coli spent years arguing that this >> behavior was confusing ( https://issues.apache.org/jira >> /browse/CASSANDRA-5836 ) , especially in the "I'm replacing a failed >> seed

Seed nodes and bootstrap (was: Re: Initializing a multiple node cluster (multiple datacenters))

On Fri, Feb 23, 2018 at 7:35 PM, Jeff Jirsa wrote: > It comes up from time to time. Rob Coli spent years arguing that this > behavior was confusing ( https://issues.apache.org/ > jira/browse/CASSANDRA-5836 ) , especially in the "I'm replacing a failed > seed" sense. I

Re: Replacing a Seed Node

On Thu, Aug 3, 2017 at 3:00 PM, Fd Habash 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 cluster has 6 nodes with

Replacing a Seed Node

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

Re: first node in a cluster - should it be a seed node

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 > wrote: > > Hello, > &

first node in a cluster - should it be a seed node

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

Re: Seed gossip version will not connect with that version

143] 2017-07-04 10:29:50,076 > OutboundTcpConnection.java:416 - Seed gossip version is -2147483648; will not > connect with that version > INFO [HANDSHAKE-/10.0.0.143] 2017-07-04 10:29:50,076 > OutboundTcpConnection.java:496 - Cannot handshake version with /10.0.0.143 > INFO [HAN

Seed gossip version will not connect with that version

Hello I have repairs that hangs because this problem WARN [MessagingService-Outgoing-/10.0.0.143] 2017-07-04 10:29:50,076 OutboundTcpConnection.java:416 - Seed gossip version is -2147483648; will not connect with that version INFO [HANDSHAKE-/10.0.0.143] 2017-07-04 10:29:50,076

stress tool: random seed

Hi, I'm populating database with YAML. Each time I run stress tool I get the same rows, i.e. the same data generated and no new rows appear. Is there any option to generate each time new data? I would like to test growing database, but don't want insert each time all data. I found a kind of worka

Re: Seed nodes as part of cluster

Awesome, thanks for clarification. So why new nodes can’t connect to ANY seed node's IP that is returned by DNS? Why the IPs must be “hardcoded”? — Roman > On May 1, 2017, at 2:11 PM, daemeon reiydelle wrote: > > Caps below for emphasis, not shouting ;{) > > Seed nodes

Re: Seed nodes as part of cluster

Caps below for emphasis, not shouting ;{) Seed nodes are IDENTICAL to all other node hdfs nodes or you will wish otherwise. Folks get confused because of terminoligy. I refer to this stuff as "the seed node service of a normal hdfs node". ANY HDFS NODE IS ABLE TO ACT AS A SEED NODE BY

Re: Seed nodes as part of cluster

So they are like any other “data” node… but special? I’m so freaking confused by this seed nodes design. — Roman > On May 1, 2017, at 1:37 PM, vasu gunja wrote: > > Seed will contain meta data + actual data too > > On Mon, May 1, 2017 at 3:34 PM, Roman Naumenko <mailto:ro

Re: Seed nodes as part of cluster

Seed will contain meta data + actual data too On Mon, May 1, 2017 at 3:34 PM, Roman Naumenko wrote: > Hi, > > I’d like to confirm that seed nodes doesn’t contain any data. Is it > correct? > > Can the instances for seed nodes be smaller size than for data nodes? >

Seed nodes as part of cluster

Hi, I’d like to confirm that seed nodes doesn’t contain any data. Is it correct? Can the instances for seed nodes be smaller size than for data nodes? Thank you Roman - To unsubscribe, e-mail: user-unsubscr

Seed Private / Public Broadcast IP

sandra can initially connect to the seed nodes via the private IP, but then the seeds provide my local instance with their brodcast_address - the public ip - and this causes problems. Is there any way to change that behavior, such that my new, local nodes ignore the broadcast_address provided to t

Re: if seed is diff on diff nodes, any problem ?

Seeds are used in two different ways: 1) When joining the ring, the joining node knows NOTHING about the cluster, so it uses a seed list to discover the cluster. Once discovered, it saves the peers to disk, so subsequent starts it will find/reconnect to other nodes beyond just the explicitly

Re: if seed is diff on diff nodes, any problem ?

As per my understanding, 2 same seed nodes per dc is the way to go.. If u r not creating two isolated set of nodes in ur cluster, there may be nodes referring each other in a way that everyone is able to know everyone else.. Anuj Sent from Yahoo Mail on Android From:"Chris M

Re: if seed is diff on diff nodes, any problem ?

I think you could end up with partitioning where a you have two cliques of nodes that gossip to each other but not to nodes outside the clique On Jul 25, 2015 3:29 PM, "rock zhang" wrote: > Hi All, > > I have 6 node, most of them are using node1 as seed, but I just find out

if seed is diff on diff nodes, any problem ?

Hi All, I have 6 node, most of them are using node1 as seed, but I just find out 2 nodes are using node3 as seed, but everything looks fine. Does that mean seed node does not have to be same on all nodes ? Thanks Rock

RE: Seed gossip version error

...@pythian.com] Envoyé : mardi 21 juillet 2015 18:33 À : user@cassandra.apache.org Objet : Re: Seed gossip version error That error should only occur when you have a mismatch between the Seed version and the new node version. Are you sure all your nodes are running in the same version? Regards, Carlos

Re: Seed gossip version error

That error should only occur when you have a mismatch between the Seed version and the new node version. Are you sure all your nodes are running in the same version? Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo | Linkedin

RE: Seed gossip version error

@cassandra.apache.org Objet : Seed gossip version error Hi, I have a running cluster running with version 2.1.7. Two of the machines went down and they are not joining the cluster even after restart. I see the following WARN message in system.log in all the nodes: system.log:WARN [MessagingService-Outgoing

Seed gossip version error

] 2015-07-01 13:00:41,878 OutboundTcpConnection.java:414 - Seed gossip version is -2147483648; will not connect with that version Please let me know if you have faced the same problem. Regards, Amlan

Re: Seed Node OOM

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 cach

Re: Seed Node OOM

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

Re: Seed Node OOM

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" wrote: > So

Re: Seed Node OOM

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 usi

Seed Node OOM

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

Re: Seed Node

On Thu, Mar 19, 2015 at 3:56 PM, jean paul 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 &

Seed Node

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.

Re: Is there harm from having all the nodes in the seed list?

On Tue, Sep 23, 2014 at 10:31 AM, Donald Smith < donald.sm...@audiencescience.com> wrote: > Is there any harm from having all the nodes listed in the seeds list in > cassandra.yaml? > Yes, seed nodes cannot bootstrap. https://issues.apache.org/jira/browse/CASSANDRA-5836 See com

Re: Is there harm from having all the nodes in the seed list?

Well, having all nodes in the seed list does not compromise any correctness of gossip protocol. However there will be extra network traffic when nodes are starting because it will ping all nodes for topology discovery, AFAIK On Tue, Sep 23, 2014 at 7:31 PM, Donald Smith < donald

Is there harm from having all the nodes in the seed list?

Is there any harm from having all the nodes listed in the seeds list in cassandra.yaml? Donald A. Smith | Senior Software Engineer P: 425.201.3900 x 3866 C: (206) 819-5965 F: (646) 443-2333 dona...@audiencescience.com [AudienceScience]

Re: Rebuilding a cassandra seed node with the same tokens and same IP address

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 b

Rebuilding a cassandra seed node with the same tokens and same IP address

, (2) stop cassandra 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

Re: 1.2.15 non-seed nodes never join cluster. JOINING: waiting for schema information to complete

On 02/11/2014 10:34 AM, sankalp kohli wrote: If you don't have a schema, you are probably hitting this https://issues.apache.org/jira/browse/CASSANDRA-6685 Looks like #6685 was committed to the cassandra-1.2 branch, yesterday. SNAPSHOT artifacts can be grabbed for the latest build of each bran

Re: 1.2.15 non-seed nodes never join cluster. JOINING: waiting for schema information to complete

If you don't have a schema, you are probably hitting this https://issues.apache.org/jira/browse/CASSANDRA-6685 On Tue, Feb 11, 2014 at 8:22 AM, John Pyeatt wrote: > I am trying to bring up a 6 node cluster in AWS. 3 seed nodes and 3 > non-seed nodes. One of each in each availabilit

1.2.15 non-seed nodes never join cluster. JOINING: waiting for schema information to complete

I am trying to bring up a 6 node cluster in AWS. 3 seed nodes and 3 non-seed nodes. One of each in each availability zone with 1.2.15 and my non-seed nodes never join the cluster. If I run 1.2.14 everything works fine. We are not using vnodes and all of the initial_token values are assigned based

Re: Query on Seed node

ys which non 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 wrote: > Hi

  1   2   >