Hi Jeff,
Anticompaction only runs before repair in the upcoming 4.0.
In all other versions of Cassandra, it runs at the end of repair sessions.
My understanding from other messages Martin sent to the ML was that he was
already running full repair not incremental, which before 4.0 will also
perform
> On Aug 3, 2019, at 5:03 PM, Martin Xue wrote:
>
> Hi Cassandra community,
>
> I am using Cassandra 3.0.14, 1 cluster, node a,b,c in DC1, node d,e,f in DC2.
>
> Keyspace_m is 1TB
>
> When I run repair -pr a full keyspace_m on node a, what I noticed are:
> 1. Repair process is running on no
Hi Cassandra community,
I am using Cassandra 3.0.14, 1 cluster, node a,b,c in DC1, node d,e,f in
DC2.
Keyspace_m is 1TB
When I run repair -pr a full keyspace_m on node a, what I noticed are:
1. Repair process is running on node a
2. Anti compaction after repair are running on other nodes at leas
Thanks to all,
I'll try the SSTables.
Thanks
Pat
On 2019-08-03 09:54, Dimo Velev wrote:
Check out the CQLSSTableWriter java class -
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/CQLSSTableWriter.java
. You use it to generate sstables - you need to wri
Check out the CQLSSTableWriter java class -
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/CQLSSTableWriter.java
. You use it to generate sstables - you need to write a small program for
that. You can then stream them over the network using the sstablelo
