Your partition key is foreignid. You may have a large partition. Why not use
foreignid+timebucket as partition key?
From: learner dba
Date: 2018-07-19 01:48
To: User cassandra.apache.org
Subject: Timeout for only one keyspace in cluster
Hi,
We have a cluster with multiple keyspaces. All queries are performing good but
write operation on few tables in one specific keyspace gets write timeout.
Table has counter column and counter update query times out always. Any idea?
CREATE TABLE x.y (
foreignid uuid,
timebucket text,
key text,
timevalue int,
value counter,
PRIMARY KEY (foreignid, timebucket, key, timevalue)
) WITH CLUSTERING ORDER BY (timebucket ASC, key ASC, timevalue ASC)
AND bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.1
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
Query and Error:
UPDATE x.y SET value = value + 1 where foreignid = ? AND timebucket = ? AND key
= ? AND timevalue = ?, err = &errors.errorString{s:\"gocql: no response
received from cassandra within timeout period
I verified CL=local_serialWe had been working on this issue for many days; any
help will be much appreciated.
