Re: which astyanax version to use?

Lijun, That is correct. If you have an investment in Astyanax , you'll need to stay in the 2.0 series. You'll either need to wait until Astyanax is updated to support 2.1 (if that is going to happen) or migrate to the datastax java driver. ~Eric On Wed, Nov 18, 2015 at 12:04 AM, Lijun Huang

Re: Replication of data over 2 Datacentre's, when one node fails we get replica issues

Hi Walsh, My comments: 1. Keeping RF at 2 and CL at LOCAL_QUORUM would not give you any additional fault tolerance. You wont be able to afford a single node failure with RF=2. I would suggest keeping it at 3 so that you can tolerate a single node failure. Your query failed because RF=2 and

Re: [Marketing Mail] Migrating to incremental repairs

Well, By re-reading my e-mail, I understood the rationale behind doing a full sequential repair for each node. I was confused by the fact that in our case, we have 3 nodes with RF = 3, so all the nodes are storing all replicas. So we are in a special case. As soon as you have more than 3

Re: Help diagnosing performance issue

Yep, I think you've mixed up your DTCS levers. I would read, or re-read Marcus's post http://www.datastax.com/dev/blog/datetieredcompactionstrategy *TL;DR:* - *base_time_seconds* is the size of your initial window - *max_sstable_age_days* is the time after which you stop compacting

Migrating to incremental repairs

Hi, We currently have a 3 nodes Cassandra cluster with RF = 3. We are using Cassandra 2.1.7. We would like to start using incremental repairs. We have some tables using LCS compaction strategy and some others using STCS. Here is the procedure written in the documentation: To migrate to

Replication of data over 2 Datacentre's, when one node fails we get replica issues

Hey all, We're testing Cassandra failover over 2 Datacentre's. There are 3 nodes on each. All CF's have a Replication of 2 on both Datacentre's (DC1:2, DC2:2) When one Datacentre goes down then all queries go to the other. This works fine for LOCAL_QUOURM queries. As 2 replicas of the data

Re: Nodetool rebuild on vnodes enabled

1. Cassandra version is 2.0.14 2. Followed doc on adding new DC . Added new DC with 3 nodes with vnodes instead of manual tokens. http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_add_dc_to_cluster_t.html 3. As per above doc and in past as well, rebuild is what i used when I

Re: Strategy tools for taking snapshots to load in another cluster instance

Hi Anishek, we are currently also thinking about how to do this in the midterm, though we don't have a test setup yet. My idea was do add one additional node to the source cluster but put it in a different DC as far as Cassandra is concerned. Using the network topology replication strategy you'd

Re: Help diagnosing performance issue

Sebastian, Robet, First, a big thank you to both of you for your help. It looks like you were right. I used pcstat (awesome tool, thanks for that as well) and it appears some files I would not expect to be in cache actually are. Here is a sample of my output (edited for convenience, adding

Strategy tools for taking snapshots to load in another cluster instance

Hello We have 5 node prod cluster and 3 node test cluster. Is there a way i can take snapshot of a table in prod and load it test cluster. The cassandra versions are same. Even if there is a tool that can help with this it will be great. If not, how do people handle scenarios where data in prod

Re: handling down node cassandra 2.0.15

@Rob interesting something i will try next time, for step 3 you mentioned -- I just remove the -Dcassandra.join_ring=false option and restart the cassandra service? @Anuj, gc_grace_seconds dictates how long hinted handoff are stored right. These might be good where we explicitly delete values

Re: Strategy tools for taking snapshots to load in another cluster instance

You can take a snapshot via nodetool then load sstables on your test cluster with sstableloader:  docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsBulkloader_t.html Sent from Yahoo Mail on Android From:"Anishek Agarwal" Date:Wed, Nov 18, 2015 at 11:24

Re: handling down node cassandra 2.0.15

Robert, This is how I interpret the implications of the 3 steps you suggested.Please confirm my interpretation as this is really important. Suppose, gc grace seconds=10days, max hinted handoff period=3 hrs, 3 nodes are there A,B & C,RF =3 and my client is reading at CL ONE. C remains down

Re: Help diagnosing performance issue

> > When you say drop you mean reduce the value (to 1 day for example), not > "don't set the value", right ? Yes. If I set max sstable age days to 1, my understanding is that SSTables with > expired data (5 days) are not going to be compacted ever. And therefore my > disk usage will keep

Re: Help diagnosing performance issue

Sebastian, Your help is very much appreciated. I re-read the blog post and also https://labs.spotify.com/2014/12/18/date-tiered-compaction/ but some things are still confusing me. Please see my questions inline below. On 11/18/2015 04:21 PM, Sebastian Estevez wrote: Yep, I think you've

Re: UnknownColumnFamily exception / schema inconsistencies

Just wanted to follow up and say thanks: I went through this process (as per Robert's suggestion, with the node stopped and no refresh) on an affected cluster and was able to resolve the issue. ​

Re: which astyanax version to use?

Eric, That's really an awful thing for me. I looked into the Astyanax code, the dependency of Cassandra is still staying on 2.0.12, and seems the community have no plan to upgrade it to support the newer version of Cassandra. But whatever, thank you so much for your reply. Thanks, Lijun Huang

Cqlsh copy to and copy from

Hi all, I have a trouble with copy functionality in cassandra 3.0. When I am trying to copy my table to file, some of UDTs have the following representation: {field1: , field2: } They have no values, and when I tried to restore this table, this rows was not imported. Do you plan to fix that,

Cassandra 3.0.0 connection problem

Hi, I'm new to Cassandra and I've recently upgraded to 3.0.0 on Ubuntu Linux 14.04 LTS, through apt-get upgrade not manual installation, after the update all was fine so I could access to my keyspaces using cqlsh but I can't access to Cassandra using DataStax PHP Driver because I get this