From: Dipan Shah [mailto:dipan@hotmail.com]
Sent: Monday, March 04, 2019 12:52 AM
To: Kenneth Brotman; user@cassandra.apache.org
Subject: Re: MV's stuck in build state
Hello Kenneth,
Apologies for the late reply.
1) On production the value of x was 67 MB and y w
ent: Friday, March 1, 2019 8:19 PM
To: user@cassandra.apache.org
Subject: RE: MV's stuck in build state
Dipan,
On your production cluster, when you were first getting the “Mutation of
bytes …” message, what was the value of x and y?
How about when you got the message on the Dev Cluster
d directly hitting the
org.apache.cassandra.db:type=CompactionManager mbean's stopCompaction
operation?
From: Dipan Shah [mailto:dipan@hotmail.com]
Sent: Friday, March 01, 2019 12:56 AM
To: Kenneth Brotman; user@cassandra.apache.org
Subject: Re: MV's stuck in build sta
creating solution over here.
Thanks,
Dipan Shah
From: Kenneth Brotman
Sent: Friday, March 1, 2019 12:26 AM
To: user@cassandra.apache.org
Subject: RE: MV's stuck in build state
Hi Dipan,
Did you try following the advice in the referenced DataStax article called
Mutation
in the stackoverflow.com post you cited?
Kenneth Brotman
From: Dipan Shah [mailto:dipan@hotmail.com]
Sent: Thursday, February 28, 2019 2:23 AM
To: Dipan Shah; user@cassandra.apache.org
Subject: Re: MV's stuck in build state
Forgot to add version info. This is on 3.7.
[cqlsh 5.0.1 | Ca
Forgot to add version info. This is on 3.7.
[cqlsh 5.0.1 | Cassandra 3.7 | CQL spec 3.4.2 | Native protocol v4]
Thanks,
Dipan Shah
From: Dipan Shah
Sent: Thursday, February 28, 2019 3:38 PM
To: user@cassandra.apache.org
Subject: MV's stuck in build
Hello All,
I have a few MV's that are stuck in build state because of a bad schema design
and thus getting a lot of messages like this "Mutation xxx is too large for
maximum size of 16.000MiB".
[cid:cde7867a-aa71-4046-97f8-7a16b1a4f3c9]
I have dropped those MV's and I can no longer see their s
