Hello,
Yes we encountered the same issue. See CASSANDRA-13125, CASSANDRA-12144, and
14008
The scrub helped us, but it took almost 4-5 hrs one 1 table of 145GB per node.
We are still scrubbing our table to resolve this issue. The next step is to
upgrade to next version as well.
Thank you
On
we also increased the max_heap_count (sysctl.conf) value to resolve OOO memory
issue.
On Thursday, 23 August 2018, 16:04:20 GMT-7, Mun Dega
wrote:
120G data28G heap out of 48 on system9 node cluster, RF3
On Thu, Aug 23, 2018, 17:19 Mohamadreza Rostami
wrote:
Hi,How much data do you
;tDate", "tid3", "sid4", "pid5")
WITH CLUSTERING ORDER BY ("tDate" ASC, "tid3" ASC, "sid4" ASC, "pid5" ASC)
On Wednesday, 22 August 2018, 15:08:03 GMT-7, dinesh.jo...@yahoo.com.INVALID
wrote:
What is the schem
Hello,
Have a table with following partition and clustering keys
partition key - ("userid", "secondaryid"),
clustering key - "tDate", "tid3", "sid4", "pid5"
Data is inserted based on above partition and clustering key. For 1 record
seeing 2 rows returned when queried by both partition and cluster
