Re: Read timeouts on primary key queries

Patrick, The desc table is below (only col names changed) : CREATE TABLE db.tbl ( id1 text, id2 text, id3 text, id4 text, f1 text, f2 map, f3 map, created timestamp, updated timestamp, PRIMARY KEY (id1, id2, id3, id4) ) WITH

Re: cassandra database design

access pattern is select *from datacenter where datacentername = '' and publish>$time and publish<$time On Wed, Aug 31, 2016 at 8:37 PM, Carlos Alonso wrote: > Maybe a good question could be: > > Which is your access pattern to this data? > > Carlos Alonso | Software

Cassandra distinct partitionkey read fails with com.datastax.driver.core.exceptions.ReadFailureException

Hi Users, One of our client deployment with single node we are experiencing Cassandra read failures through java client for below query . I could see similar error through cqlsh client as well. This was working fine few months started happening couple of days ago. We might be having close to 10

Question about end of life support for Apache Cassandra 2.1 and 2.2

According to the download page, Apache Cassandra 2.1 is supported with critical fixes only till Nov 2016 and and Apache Cassandra 2.2 is supported till Nov 2016. I wanted to know what is the policy for such "unsupported" versions, especially related to

mutation checksum failure during commit log replay

What could cause an error like: ERROR 07:11:56 Exiting due to error while processing commit log during initialization. org.apache.cassandra.db.commitlog.CommitLogReplayer$CommitLogReplayException: Mutation checksum failure at 818339 in CommitLog-5-1470234746867.log This is with Cassandra 2.2.4.

testing retry policy

hi all, I have some customized retry policies that want to test. In my single node local cluster, is there anyway to simulate the read/write timeout and or unavailable exception? I tried to kill the Cassandra process but it won't result in unavailable exception but no host available exception and

Replication time across regions in AWS

Has anybody tested time taken to replicate data across regions between us-east and west or AZ in AWS? Few docs/blogs says its in few 10s of millisecs. Please can you provide your insights. Also is there a way to measure the time lag.

Re: Read timeouts on primary key queries

If you are getting a timeout on one table, then a mismatch of RF and node count doesn't seem as likely. Time to look at your query. You said it was a 'select * from table where key=?' type query. I would next use the trace facility in cqlsh to investigate further. That's a good way to find hard

unsubscribe

Re: LCS Increasing the sstable size

Hello DuyHai, I have no problem with performance even if I'm using 3 HDD in RAID 0. Last 4 years of data were imported in two weeks with is acceptable for the client. Daily data will be much less intensive and my client is more concerned with storage price than with pure latency. To be more

Re: cassandra database design

Maybe a good question could be: Which is your access pattern to this data? Carlos Alonso | Software Engineer | @calonso On 31 August 2016 at 11:47, Stone Fang wrote: > Hi all, > have some questions on how to define clustering key. > > have

Re: LCS Increasing the sstable size

Some random thoughts 1) Are they using SSD ? 2) If using SSD, I remember that one recommendation is not to exceed ~3Tb/node, unless they're using DateTiered or better TimeWindow compaction strategy 3) LCS is very disk intensive and usually exacerbates write amp the more you have data 4) The

LCS Increasing the sstable size

Hello, My cluster use LeveledCompactionStrategy on rather big nodes (9 TB disk per node with a target of 6 TB of data and the 3 remaining TB are reserved for compaction and snapshots). There is only one table for this application. With default sstable_size_in_mb at 160 MB, we have a huge number

cassandra database design

Hi all, have some questions on how to define clustering key. have a table like this CREATE TABLE datacenter{ datacentername varchar, publish timestamp, value varchar, PRIMARY KEY(datacentername,publish) } *issues:* there are only two datacenter,so the data would only have two

Re: Output of "select token from system.local where key = 'local' "

. P On Wednesday, 31 August 2016, Alexander DEJANOVSKI wrote: > Hi Siddharth, > > yes, we are sure token ranges will never overlap (I think the start token > in describering output is excluded and the end token included). > > You can get per host information in the