Hi,
I am currently benchmarking Cassandra with three machines, and on each
machine I am seeing an unbalanced distribution of data among the data
directories (1 per disk).
I am concerned that this affects my write performance, is there anything
that I can make the distribution be more even? Would r
We've recently started upgrading from 1.2.12 to 2.1.7. In 1.2.12 we
wrote code that used the well-known pagination pattern (tokens) to
process all rows in one of our tables. For 2.1.7 we tried replacing
that code with the new built-in pagination code:
List queryRows = new ArrayList<>();
Hi all,
I've been upgrading several of our rings from 2.1.6 to 2.1.8 and I've
noticed that after the upgrade our storage load drops significantly (I've
seen up to an 80% drop).
I believe most of the data that is dropped is tombstoned (via TTL
expiration) and I haven't detected any data loss yet.
Hello John,
Below are the situations where a snapshot is automatically taken on 1.2:
1. during compactions, if snapshot_before_compaction yaml option is set to
true, in this case, the snapshot name will be -compact-.
2. when you drop or truncate a CF, when auto_snapshot yaml option is set to
true
Thanks for your answer Tyler.
Unfortunately, I can't wait for 3.x to be released.
I think I will update my schema to declare explicitely all columns with
predictive names and I will migrate only the dynamic ones to a new table.
This will reduce drastically the amount of data to migrate and I'll b
