Re: Setting bloom_filter_fp_chance < 0.01

Bloom filters are used to avoid disk seeks on accessing sstables. As we don't know where exactly the partition resides, we have to narrow down the search to paticular sstables where the data most probably is. Given that most likely you won't store 50B rows on the single node, you will most likely

Re: Intermittent CAS error

I bet that’s it. I have a shared library that I use with another project that is still on 2.0, so I’ve kept the driver at 2.0. The issue was addressed in version 2.1 of the driver. Thanks On May 19, 2016, at 9:03 AM, Joel Knighton mailto:joel.knigh...@datastax.com>> wrote: That particular err

Re: Intermittent CAS error

That particular error is thrown directly from the Java driver (unless it is also copied in other drivers, either way, not from Cassandra). There has been a bug related to this in the past - JAVA-764 . You may be on an affected version, or you may

Re: Setting bloom_filter_fp_chance < 0.01

with 50 bln rows and bloom_filter_fp_chance = 0.01, bloom filter will consume a lot of off heap memory. You may want to take that into consideration too. On Wed, May 18, 2016 at 11:53 PM, Adarsh Kumar wrote: > Hi Sai, > > We have a use case where we are designing a table that is going to have >

RE: Replication lag between data center

Just wanted to chime in that this is a very well-written and explained answer. Nice job, Jeff! Sean Durity From: Jeff Jirsa [mailto:jeff.ji...@crowdstrike.com] Sent: Wednesday, May 18, 2016 11:41 PM To: user@cassandra.apache.org Subject: Re: Replication lag between data center Cassandra isn’t a

Re: Recovery for deleted SSTables files for one column family.

Hi Ben, the scenario that I was trying to test was all sstables (deleted) from one node. So I did what you suggested (rebuild the sstables from other replicas in the cluster) and it rebuilt the sstables successfully. I think the reason that I didn't see the sstables rebuilt earlier on was because

Re: Recovery for deleted SSTables files for one column family.

Use nodetool listsnapshots to check if you have a snapshot - in default configuration, Cassandra takes snapshots for operations like truncate. Failing that, is it all sstables from all nodes? In this case, your data has gone I’m afraid. If it’s just all sstables from one node then running repair w

Recovery for deleted SSTables files for one column family.

Hi all, I would like to know, is there any way to rebuild a particular column family when all the SSTables files for this column family are missing?? Say we do not have any backup of it. Thank you. Regards, Mike Yeap