Hi Alexander, yes we use MV’s. The size of the batch table is around 10GB on the existing nodes. Also seems pretty high. So is this table (also) used to process MV building?
Regards, 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@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 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 model ? You just bootstrapped a new node and the table grew on all other nodes ? On Thu, Dec 7, 2017 at 12:25 PM Christian Lorenz <christian.lor...@webtrekk.com<mailto:christian.lor...@webtrekk.com>> wrote: 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 -- ----------------- Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com<http://www.thelastpickle.com/>
