Re: Basic query in setting up secure inter-dc cluster

Thanks everyone for the reply. I actually have a fair bit of questions, but it will be nice if someone could please tell me the flow (implementation-wise), as to how node-to-node encryption works in a cluster. Let's say node1 from DC1, wishes to talk securely to node 2 from DC2 (with

Re: Node stuck when joining a Cassandra 2.2.0 cluster

Hi, Thanks for the tip. I found that one keyspace was kinda corrupted. It was previously scrubbed/deleted but there where files left in the servers, so it was in a strange state. After removing it from the filesystem I was able to add the new node to the cluster. Since this keyspace was in an

Re: Basic query in setting up secure inter-dc cluster

Hi Ajay, Have a look here : https://docs.datastax.com/en/cassandra/1.2/cassandra/security/secureSSLNodeToNode_t.html You can configure for DC level Security: Procedure On each node under sever_encryption_options: - Enable internode_encryption. The available options are: - all

Re: Data Modeling: Partition Size and Query Efficiency

On Tue, Jan 5, 2016 at 5:52 PM, Jonathan Haddad wrote: > You could keep a "num_buckets" value associated with the client's account, > which can be adjusted accordingly as usage increases. > Yes, but the adjustment problem is tricky when there are multiple concurrent writers.

New node has high network and disk usage.

Hi, We recently added a new node to our cluster in order to replace a node that died (hardware failure we believe). For the next two weeks it had high disk and network activity. We replaced the server, but it's happened again. We've looked into memory allowances, disk performance, number of

Re: New node has high network and disk usage.

I should probably have mentioned that we're on Cassandra 2.0.10. On 6 January 2016 at 15:26, Vickrum Loi wrote: > Hi, > > We recently added a new node to our cluster in order to replace a node > that died (hardware failure we believe). For the next two weeks it had

Formal EOL for 2.0.17 and 2.1.12

Hi, Can someone help me by providing formal dates of EOL for Cassandra 2.0.17 and 2.1.12? ThanksAnuj Sent from Yahoo Mail on Android

Re: New node has high network and disk usage.

What’s your output of `nodetool compactionstats`? > On Jan 6, 2016, at 7:26 AM, Vickrum Loi wrote: > > Hi, > > We recently added a new node to our cluster in order to replace a node that > died (hardware failure we believe). For the next two weeks it had high

Re: New node has high network and disk usage.

Hi Vickrum, I would have proceeded with diagnosis as follows: 1. Analysis of sar report to check system health -cpu memory swap disk etc.  System seems to be overloaded. This is evident from mutation drops. 2. Make sure that  all recommended Cassandra production settings available at Datastax

Re: Cassandra Performance on a Single Machine

Anurag, Unless you are planning on continuing to use only one machine with RF=1 benchmarking a single system using RF=Consistancy=1 is mostly a waste of time. If you are going to use RF=1 and a single host then why use Cassandra at all. Plain old relational dbs should do the job just fine.

Re: opscenter doesn't work with cassandra 3.0

On 01/06/2016 01:47 AM, Wills Feng wrote: > Looks like opscenter doesn't support cassandra 3.0? This is correct. OpsCenter does not support Cassandra >= 3.0. -- Michael

Re: opscenter doesn't work with cassandra 3.0

On 01/06/2016 10:55 AM, Michael Shuler wrote: > On 01/06/2016 01:47 AM, Wills Feng wrote: >> Looks like opscenter doesn't support cassandra 3.0? > > This is correct. OpsCenter does not support Cassandra >= 3.0. It took me a minute to find the correct document:

Re: New node has high network and disk usage.

# nodetool compactionstats pending tasks: 22 compaction typekeyspace table completed total unit progress Compactionproduction_analyticsinteractions 240410213161172668724 bytes 0.15%

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

Hi Rob, I want to make sure I am not missing anything on my side before creating a jira ticket with Cassandra. I will wait for others to respond before filing a ticket. May be somebody can give me a clue of what might be going wrong. This

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

On 01/06/2016 03:57 PM, Peddi, Praveen wrote: > This blog > > claims Cassandra is now 50% faster. We are obviously not seeing that. That post compared cassandra-stress write on versions 2.0 and 2.1, each on a single AWS

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

Hi Michael, I am not comparing my results with results on that page. I mentioned only in the context of improved performance in 2.1 compared to 2.0. That page compares performance between 2.0 and 2.1 with same hardware. I am doing the same exact thing (running 2.0.9 and 2.1.11 on same hardware,

Re: Revisit Cassandra EOL Policy

I would appreciate if you guys share your thoughts on the concerns I expressed regarding Cassandra End of Life policy. I think these concerns are quite genuine and should be openly discussed so that EOL is more predictable and generates less overhead for the users. I would like to understand

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

Anecdotal evidence typically agrees that 2.1 is faster than 2.0 (our experience was anywhere from 20-60%, depending on workload). However, it’s not necessarily true that everything behaves exactly the same – in particular, memtables are different, commitlog segment handling is different, and

confusion about migrating to incremental repair

Hi, I am running a cluster with 2.2.4. I have some table on LCS and plan to use incremental repair. I read the post at http://www.datastax.com/dev/blog/anticompaction-in-cassandra-2-1 and am a little confused. especially: "This means that *once you do an incremental repair you will have to

Re: Re: Fail to export all data in C* cluster

Cassandra does not have any automatic rollback of partial work for a failed write request, if with CL=ALL - that just assures that you will get an error indication if not all the writes succeed. You do need to keep retrying failed writes until they succeed. Otherwise the partial work will still be

Slow performance after upgrading from 2.0.9 to 2.1.11

Hi, We have upgraded Cassandra from 2.0.9 to 2.1.11 in our loadtest environment with pretty much same yaml settings in both (removed unused yaml settings and renamed few others) and we have noticed performance on 2.1.11 is worse compared to 2.0.9. After more investigation we found that the

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

On Wed, Jan 6, 2016 at 11:41 AM, Peddi, Praveen wrote: > We have upgraded Cassandra from 2.0.9 to 2.1.11 in our loadtest > environment with pretty much same yaml settings in both (removed unused > yaml settings and renamed few others) and we have noticed performance on > 2.1.11

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2nd column is replication factor (RF). I have 2 rows for reads and 2 for writes. First row is RF=1 and 2nd row is RF=3. So when I said increasing RF , I meant from 1 to 3. Sorry the table is probably not clear. Praveen From: Robert Coli

Re: Formal EOL for 2.0.17 and 2.1.12

Back in June, Jonathan posted: "After 2.2.0 is released, 2.0 will reach end-of-life as planned. After 3.0.0 is released, 2.1 will also reach end of life. This is earlier than expected, but 2.2 will be very close to as stable as 2.1 and users will be well served by upgrading. We will maintain the

Re: CQL Composite Key Seen After Table Creation

On Wed, Jan 6, 2016 at 12:54 PM, Chris Burroughs wrote: > I work with Amir and further experimentation I can shed a little more > light on what exactly is going on under the hood. For background our goal > is to take data that is currently being read and written to

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

On Wed, Jan 6, 2016 at 11:49 AM, Peddi, Praveen wrote: > 2nd column is replication factor (RF). I have 2 rows for reads and 2 for > writes. First row is RF=1 and 2nd row is RF=3. So when I said increasing RF > , I meant from 1 to 3. Sorry the table is probably not clear. > Ah,

Re: CQL Composite Key Seen After Table Creation

I work with Amir and further experimentation I can shed a little more light on what exactly is going on under the hood. For background our goal is to take data that is currently being read and written to via thrift, switch reads to CQL, and then switch writes to CQL. This is in alternative to