Sorry about the confusion.
I meant the sstables for system.batches table which got created after dropping
the MV still persist and have huge size.
Original Message
Subject: Re: Huge size of system.batches table after dropping an incomplete
Materialized View
Local Time: 23
t node.
>
>
> ---- Original Message ----
> Subject: Re: Huge size of system.batches table after dropping an
> incomplete Materialized View
> Local Time: 22 January 2017 11:41 PM
> UTC Time: 22 January 2017 18:11
> From: benjamin.r...@jaumo.com
> To: user@cassandra.apache.org, Vi
timestamps.
Not sure if i can safely rm these sstables or truncate system.batches on that
node.
Original Message
Subject: Re: Huge size of system.batches table after dropping an incomplete
Materialized View
Local Time: 22 January 2017 11:41 PM
UTC Time: 22 January 2017 18:11
I cannot tell you were these errors like "Attempting to mutate ..." come
from but under certain circumstances all view mutations are stored in
batches, so the batchlog can grow insanely large. I don't see why a repair
should help you in this situation. I guess what you want is to recreate the
Hi there,
Version :- Cassandra 3.0.7
I attempted to create a Materialized View on a certain table and it failed with
never-ending WARN message "Mutation of bytes is too large for the maximum
size of ".
"nodetool stop VIEW_BUILD" also did not help.
That seems to be a result of
