o process MV building?
>>
>>
>>
>> Regards,
>>
>> Christian
>>
>> *Von: *Alexander Dejanovski <a...@thelastpickle.com>
>> *Antworten an: *"user@cassandra.apache.org" <user@cassandra.apache.org>
>> *Datum: *Donnerstag, 7
;
> Christian
>
> *Von: *Alexander Dejanovski <a...@thelastpickle.com>
> *Antworten an: *"user@cassandra.apache.org" <user@cassandra.apache.org>
> *Datum: *Donnerstag, 7. Dezember 2017 um 16:24
> *An: *"user@cassandra.apache.org" <user@cassand
.org" <user@cassandra.apache.org>
Datum: Donnerstag, 7. Dezember 2017 um 16:24
An: "user@cassandra.apache.org" <user@cassandra.apache.org>
Betreff: Re: Huge system.batches table after joining a node (Cassandra 3.11.1)
Hi Christian,
it is probably not safe to drop it
Hi Christian,
it is probably not safe to drop it because it contains all logged batches
that are supposed to be played on the cluster.
The size of the batches table should go down as they get processed
(although 100GB is a pretty huge batch log...)
Do you use Materialized Views in your data
Hi,
after joining a node into an existing cluster, the table system.batches became
quite large (100GB) which is about 1/3 of the nodes size.
Is it safe to truncate the table?
Regards,
Christian