RE: Seed List

Subject: Re: Seed List EXTERNAL 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 prov

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 different (perha

RE: Seed List

It can work to use host names. We have done it for temporary clusters where there is at least a theoretical possibility of an ip address change. I don't know all the trade-offs of using host names, since we don't do that for production. Sean R. Durity INTERNAL USE -Original Message-

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

On Tue, Mar 6, 2018 at 8:28 PM, Jeff Jirsa wrote: > > Sorry, I wasnt as precise as I should have been: > > In 3.0 and newer, a bootstrapping node will wait until it has schema > before it bootstraps. HOWEVER, we make the ssystem_auth/system_distributed, > etc keyspaces as a node starts up, before

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

On Tue, Mar 6, 2018 at 9:50 AM, Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > On 6 Mar 2018 16:55, "Jeff Jirsa" wrote: > > On Mar 6, 2018, at 12:32 AM, Oleksandr Shulgin < > oleksandr.shul...@zalando.de> wrote: > > On 5 Mar 2018 16:13, "Jeff Jirsa" wrote: > > On Mar 5, 2018, at 6:40

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 we have noticed that all

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 total) >> and we have noticed that all se

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: KeyspaceMetadata{name=syst

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: KeyspaceMetadata{name=system_traces, > p

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

That ticket was before I was really active contributing, but I tend to agree with your assessment: clearly there's pain point there, and we can do better than the status quo. The problem (as Jonathan notes) is that its a complicated subsystem, and the "obvious" fix probably isn't as obvious as it

Re: Seed gossip version will not connect with that version

Restart could help with hung gossip but check you network as possible root cause for this. Sent from my iPhone > On Jul 5, 2017, at 7:23 AM, Jean Carlo wrote: > > Hello > > I have repairs that hangs because this problem > > WARN [MessagingService-Outgoing-/10.0.0.143] 2017-07-04 10:29:50,07

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 are IDENTICAL to all ot

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

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 >

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? > > Thank you > Roman > -

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: *linkedin.c

RE: Seed gossip version error

Hi Amlan, We have the same pb with Cassandra 2.1.5. I have no hint (yet) to follow. Did you found the root of this pb ? Thanks. Regards, Dominique [@@ THALES GROUP INTERNAL @@] De : Amlan Roy [mailto:amlan@cleartrip.com] Envoyé : mercredi 1 juillet 2015 12:46 À : user@cassandra.apache.o

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

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 "a seed" is within Cassandra

Re: Seed vs non-seed in YAML

> Seeds will not auto-bootstrap themselves when you add them to  the cluster. And having a bunch of nodes that aren't even in the cluster (when you move them around, decommission etc) seems like a bad idea. As for amount: I would say definitely have at least RF seeds (for some reason I haven't he

Re: Seed nodes in cassandra.yaml can not be hostnames

Dne 26.9.2011 16:37, Jonathan Ellis napsal(a): The seed names should match what the seeds advertise as listen_address. I can't think of a reason host names shouldn't work, I used DNS alias, that was probably reason why it didn't worked.

Re: Seed nodes in cassandra.yaml can not be hostnames

The seed names should match what the seeds advertise as listen_address. I can't think of a reason host names shouldn't work, but as Peter said, using host names is a bad idea anyway. 2011/9/25 Radim Kolar : > I just discovered that using host names for seed nodes in cassandra.yaml do > not work.

Re: Seed nodes in cassandra.yaml can not be hostnames

> I just discovered that using host names for seed nodes in cassandra.yaml do > not work. This is done on purpose? I believe so yes, to avoid relying on DNS to map correctly given that everything else is based on IP address. (IIRC, someone chime in if there is a different reason.) -- / Peter Sch

Re: Seed vs non-seed in YAML

Seeds will not auto-bootstrap themselves when you add them to the cluster. Normal approach is to have 2 or 3 per DC. You may also be interested in how Gossip uses the seed list http://wiki.apache.org/cassandra/ArchitectureGossip cheers - Aaron Morton Freelance Cassandra De

Re: seed faq

Done. Thank you for your comment. maki 2011/4/24 aaron morton : > May also want to add that seed nodes do not auto bootstrap. > > Thanks > Aaron

Re: seed faq

May also want to add that seed nodes do not auto bootstrap. Thanks Aaron On 22 Apr 2011, at 13:24, Maki Watanabe wrote: > Thank you, Naren. > I'll add some more details and upload it to FAQ wiki page. > > maki > > 2011/4/21 Narendra Sharma : >> Here are some more details that might help: >> 1.

Re: seed faq

Thank you, Naren. I'll add some more details and upload it to FAQ wiki page. maki 2011/4/21 Narendra Sharma : > Here are some more details that might help: > 1. You are right that Seeds are referred on startup to learn about the ring. > 2. It is a good idea to have more than 1 seed. Seed is not S

Re: seed faq

Here are some more details that might help: 1. You are right that Seeds are referred on startup to learn about the ring. 2. It is a good idea to have more than 1 seed. Seed is not SPoF. Remember Gossip also provides eventual consistency. So if seed is missing, the new node may not have the correct

Re: Seed

That is from the wiki http://wiki.apache.org/cassandra/StorageConfiguration http://wiki.apache.org/cassandra/StorageConfiguration -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Seed-tp6162837p6174450.html Sent from the cassandra-u...@incubator.

Re: Seed

What page is that from ? Aaron On 15 Mar 2011, at 06:20, mcasandra wrote: > > Tyler Hobbs-2 wrote: >> >> Seeds: >> Never use a node's own address as a seed if you are bootstrapping it by >> setting autobootstrap to true! >> > > I came accross this on the wiki. Can someone please help me und

Re: Seed

Tyler Hobbs-2 wrote: > > Seeds: > Never use a node's own address as a seed if you are bootstrapping it by > setting autobootstrap to true! > I came accross this on the wiki. Can someone please help me understand this with some example? -- View this message in context: http://cassandra-user-i

Re: Seed

On Fri, Mar 11, 2011 at 2:55 PM, mcasandra wrote: > My question is it advisable to have node seed itself. > Yes, every node should have the same seed list, including the seeds themselves. -- Tyler Hobbs Software Engineer, DataStax Maintainer of the pycassa

Re: Seed Nodes

The seed list is also used as part of the Gossip round http://wiki.apache.org/cassandra/ArchitectureGossip I agree it's not critical to ensure all running nodes have the same running seed list. But it's definitely a good idea. Disclaimer: Learning more about the gossip protocol is on my to-do list

Re: Seed Nodes

You do not need to restart when changing the seedlist of nodes that are up. The seedlist is really only used when a node first starts. So if you modify the list of seeds the changes will take effect whenever that node restarts, exactly when they need to. In 0.7 you can basically get away with igno

Re: Seed Nodes

Yes, two per DC is a recommendation I've heard from Jonathan Ellis. We put that in yet more documentation athttp://www.datastax.com/dev/tutorials/getting_started_0.7/configuring#seed-list(appreciate the citation Aaron :) I had a recent conversation with a Cassandra expert who had me convinced tha

Re: Seed Nodes

AFAIK it's recommended to have two seed nodes per dc. Some info on seeds here http://www.datastax.com/docs/0.7/operations/clustering You will need a restart. Aaron On 2/03/2011, at 6:08 AM, shan...@accenture.com wrote: > How many seed nodes should I have for a cluster of 100 nodes each with ab

Re: seed node failure crash the whole cluster

i will continue the issue here: http://groups.google.com/group/scale7/browse_thread/thread/dd74f1d6265ae2e7 thanks On Tue, Feb 8, 2011 at 7:44 AM, Dan Washusen wrote: > Hi, > I've added some comments and questions inline. > > Cheers, > Dan > On 8 February 2011 10:00, Jonathan Ellis wrote: >>

Re: seed node failure crash the whole cluster

Hi, I've added some comments and questions inline. Cheers, Dan On 8 February 2011 10:00, Jonathan Ellis wrote: > On Mon, Feb 7, 2011 at 1:51 AM, TSANG Yiu Wing wrote: > > cassandra version: 0.7 > > > > client library: scale7-pelops / 1.0-RC1-0.7.0-SNAPSHOT > > > > cluster: 3 machines (A, B, C)

Re: seed node failure crash the whole cluster

On Mon, Feb 7, 2011 at 1:51 AM, TSANG Yiu Wing wrote: > cassandra version: 0.7 > > client library: scale7-pelops / 1.0-RC1-0.7.0-SNAPSHOT > > 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 hap

Re: Seed and nodetool

Can you do an insert with CL ALL?Are there any ERRORs in the log file? Try turning the logging up the TRACE and see whats happening. Check B and see A by ssh'ing into B and using node tool from there to connect to A. Do you have any switches / firewalls between the nodes ? Could this be happenin

Re: Seed and nodetool

BTW, A is 192.168.11.29 B is 192.168.11.28 C is 192.168.11.27 from the result of nodetool ring, does it mean that B thinks A, C are down and C thinks B is down? I tried to restart B and for a bring moment, I didn't get this problem (all the nodes are all from nodetool) but after a while, this