Re: Adding new nodes to cluster to speedup pending compactions

s, or event an occasional one time > cluster required to spin up for some analysis before being spun down? This > info helps a lots in understanding where you can make concessions. > - What is the flow of data and what are the timing requirements? > > Cheers, > Eevee. >

Re: Adding new nodes to cluster to speedup pending compactions

ytes=>GB > > You are storing 1Tb per node, so long running compaction is not really a > surprise, you can play with concurrent compaction thread number, compaction > throughput to begin with > > > On 27 April 2018 at 16:59, Mikhail Tsaplin wrote: > >> Hi, >> I

Adding new nodes to cluster to speedup pending compactions

Hi, I have a five nodes C* cluster suffering from a big number of pending compaction tasks: 1) 571; 2) 91; 3) 367; 4) 22; 5) 232 Initially, it was holding one big table (table_a). With Spark, I read that table, extended its data and stored in a second table_b. After this copying/extending process

Why nodetool cleanup should be run sequentially after node joined a cluster

Hi, In https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddNodeToCluster.html there is recommendation: 6) After all new nodes are running, run nodetool cleanup on each of the previously existing nodes

Removing initial_token parameter

Is it safe to remove initial_token parameter on a cluster created by snapshot restore procedure presented here https://docs.datastax.com /en/cassandra/latest/cassandra/operations/opsSnapshotRestoreNewCluster.html ? For me, it seems that initial_token parameter is used only when nodes are started t

Re: Joining a cluster of nodes having multi valued initial_token parameters.

I suspect that cluster was created by recovering from a snapshot. PS. I asked a related question on this mailing list. Please check subject: Removing initial_token parameter. 2018-03-08 20:02 GMT+07:00 Oleksandr Shulgin : > On Thu, Mar 8, 2018 at 1:41 PM, Mikhail Tsaplin > wrote: >

Re: Joining a cluster of nodes having multi valued initial_token parameters.

Thank you for the answer, are you sure that it at least safe? As I understand I will have to specify auto_bootstrap=true too? 2018-03-08 18:16 GMT+07:00 Oleksandr Shulgin : > On Thu, Mar 8, 2018 at 12:09 PM, Mikhail Tsaplin > wrote: > >> Hi, >> >> I have a three no

Joining a cluster of nodes having multi valued initial_token parameters.

Hi, I have a three node Cassandra cluster. Every node has initial_token configuration parameter holding 256 tokens (looks like randomly distributed). Now I have to add a fourth node. How could this be done? PS. Part of 'nodetool ring' output: 192.168.1.123 rack1 Up Normal 2.84 T

Re: Cqlsh unable to switch keyspace after Cassandra upgrade.

Yesterday found problem source. It was because of old cassandra-driver for python language. Driver removal and pip install solved the issue. 2017-11-02 20:33 GMT+07:00 Blake Eggleston : > Looks like a bug, could you open a jira? > > > On Nov 2, 2017, at 2:08 AM, Mikhail Tsaplin w

Cqlsh unable to switch keyspace after Cassandra upgrade.

Hi, I've upgraded Cassandra from 2.1.6 to 3.0.9 on three nodes cluster. After upgrade cqlsh shows following error when trying to run "use {keyspace};" command: 'ResponseFuture' object has no attribute 'is_schema_agreed' Actual upgrade was done on Ubuntu 16.04 by running "apt-get upgrade cassandra"

Handling quorum writies fails

Hi. According to Datastax documentation about atomicity in Cassandra: QUORUM write succeeded only on one node will not be rolled back (Check Atomicity chapter there: http://www.datastax.com/documentation/cassandra/1.2/webhelp/index.html#cassandra/dml/dml_about_transactions_c.html). So when I am pe