Historical data movement to other cluster

2017-09-12 Thread Harika Vangapelli -T (hvangape - AKRAYA INC at Cisco)
Is there a way to move past 3 months data from one cassandra cluster to other cluster? Thanks, Harika [http://wwwin.cisco.com/c/dam/cec/organizations/gmcc/services-tools/signaturetool/images/logo/logo_gradient.png] Harika Vangapelli Engineer - IT hvang...@cisco.com

Rebalance a cassandra cluster

2017-09-12 Thread Akshit Jain
Hi, Can a cassandra cluster be unbalanced in terms of data? If yes then how to rebalance a cassandra cluster.

RE: Cassandra downgrade of 2.1.15 to 2.1.12

2017-09-12 Thread Mark Furlong
Great information. Thank you Mark 801-705-7115 office -Original Message- From: Michael Shuler [mailto:mshu...@pbandjelly.org] On Behalf Of Michael Shuler Sent: Monday, September 11, 2017 5:54 PM To: user@cassandra.apache.org Subject: Re: Cassandra downgrade of 2.1.15 to 2.1.12 On

Re: Cassandra compatibility matrix

2017-09-12 Thread Andy Tolbert
Hi Dmitry, We are currently working on updating our matrices for the drivers, but any version of driver 3.0+ will work with cassandra 3.X. Thanks, Andy On Tue, Sep 12, 2017 at 12:30 PM Dmitry Buzolin wrote: > Thank you Jon. > > Is there way to find what Datastax driver

Re: Cassandra compatibility matrix

2017-09-12 Thread Dmitry Buzolin
Thank you Jon. Is there way to find what Datastax driver is compatible with Cassandra 3.11? http://docs.datastax.com/en/developer/driver-matrix/doc/javaDrivers.html#java-drivers For some reason they don’t

Can't access Cassandra on remote node

2017-09-12 Thread Andrea Giordano
Hi, I’m using cassandra on a remote node I can access just with console. Since the node has a private ip, the cluster manager set a proxy to access private_ip:9042 in order to allow me to execute query against the db, so I have a public ip:port. Unfortunately I’m not able to execute query and

Re: Do not use Cassandra 3.11.0+ or Cassandra 3.0.12+

2017-09-12 Thread Jeff Jirsa
On the user side: 3.11.0 or 3.0.14 is probably what you want to use for new clusters as long as you can avoid calling the getTombstoneRatio() mbean with your metrics gathering tools. On Tue, Sep 12, 2017 at 8:35 AM, Sandeep S wrote: > Hi, > > What is the current

Re: load distribution that I can't explain

2017-09-12 Thread kaveh minooie
Hi kurt, thanks for responding. I understand that that query is very resource consuming. My question was why I only see its effect on the same node? considering that I have a replication factor of 2, I was hoping to see this load evenly distributed among those 2 nodes. That query runs

Re: Do not use Cassandra 3.11.0+ or Cassandra 3.0.12+

2017-09-12 Thread Chris Lohfink
Last Ive seen of it OpsCenter does not collect this metric. I don't think any monitoring tools do. Chris > On Sep 11, 2017, at 4:06 PM, CPC wrote: > > Hi, > > Is this bug fixed in dse 5.1.3? As I understand calling jmx getTombStoneRatio > trigers that bug. We are using

RE: Can I have multiple datacenter with different versions of Cassandra

2017-09-12 Thread Durity, Sean R
No – the general answer is that you cannot stream between major versions of Cassandra. I would upgrade the existing ring, then add the new DC. Sean Durity From: Chuck Reynolds [mailto:creyno...@ancestry.com] Sent: Thursday, May 18, 2017 11:20 AM To: user@cassandra.apache.org Subject: Can I

RE: Reg:- DSE 5.1.0 Issue

2017-09-12 Thread Durity, Sean R
In an attempt to help close the loop for future readers… I don’t think an upgrade from DSE 4.8 straight to 5.1 is supported. I think you have to go through 5.0.x first. And, yes, you should contact DataStax support for help, but I’m ok with DSE-related questions. They may be more

RE: AWS Cassandra backup/Restore tools

2017-09-12 Thread Durity, Sean R
Datos IO has a backup/restore product for Cassandra that another team here has used successfully. It solves many of the problems inherent with sstable captures. Without something like it, restores are a nightmare with any volume of data. The downtime required and the loss of data since the

Re: Cassandra 3.11 is compacting forever

2017-09-12 Thread Ioannis Zafiropoulos
A maybe long shot, have you deleted the cassandra-topology.properties file since you are using GossipingPropertyFileSnitch? I am sure I have seen a ticket about problems caused in some cases if that file stays around. I removed it from all the nodes and non-stop compaction stopped (after a proper