sstable corruption and schema migration issues

which versions of cassandra 2.x and 3.x are best for avoiding sstable corruption and schema migration slowness? is this a "cassandra is not a set it and forget it system" concept?

RE: Cassandra 2.2.7 Compaction after Truncate issue

Chief Executive Officer m 202.905.2818 Anant Corporation 1010 Wisconsin Ave NW, Suite 250 Washington, D.C. 20007 We build and manage digital business technology platforms. On Aug 14, 2018, 11:49 AM -0500, David Payne mailto:dav...@cqg.com>>, wrote: Scenario: Cassandra 2.2.7, 3 nodes

RE: Cassandra 2.2.7 Compaction after Truncate issue

mp;data=02%7C01%7C%7C7231eb88a6154a6520bf08d60964367b%7C0f96d359c20349d1a42dcbb27249db0d%7C0%7C0%7C636706723366003689&sdata=p0KhN5D2H%2B1bZ%2B2jeOXSV8OSaRCJTqHmH6ffFzwwfNU%3D&reserved=0> Washington, D.C. 20007 We build and manage digital business technology platforms. On Aug 14, 2018, 11:49 AM -0500, David Payne m

Cassandra 2.2.7 Compaction after Truncate issue

compaction for the truncated table for node 2 and 3, but not node 1. This appears to be a defect that was fixed in 2.1.0. https://issues.apache.org/jira/browse/CASSANDRA-7803 Any ideas? Thanks, David Payne |￣￣| ＿☆☆☆＿ （ ´_⊃｀） c. 303-717-0548 dav...@cqg.com<mailto:dav...@cqg.com>

FailureDetector.java:456 - Ignoring interval time

-L474 MAX_INTERVAL_IN_NANO seems to be how this is controlled. Where does the result of getMaxInterval() which sets MAX_INTERVAL_IN_NANO come from? Thanks, David Payne |￣￣| ＿☆☆☆＿ （ ´_⊃｀） c. 303-717-0548 dav...@cqg.com<mailto:dav...@cqg.com>

Incremental Backup Hardlinks

Hello Cassandra Experts and Committers, Hopefully this is just a dumb question, but without the skill set to read the source code, I must ask. Consider incremental backups are enabled on 2.x or 3.x. As memtables flush to sstables on disk, hardlinks are created in backups for the column family.