What happens is that when trying to rebuild the MV, the rebuilder tries to create a very large batch that exceeds commitlog_segment_size_in_mb. This limitation is currently being addressed on CASSANDRA-11670. Two options I can see to workaround this for now: 1) increase commitlog_segment_size_in_mb as you suggested 2) Re-create the base table and views and reinsert all data again to the base able.
2016-08-08 19:52 GMT-03:00 Jason J. W. Williams <jasonjwwilli...@gmail.com>: > HI Guys, > > We're running Cassandra 3.0.8, and needed to add a field to a table and > it's materialized views. We dropped the MVs, added the fields to the > underlying table, and recreated MVs with the new fields. However, the MV > creation is failing with: > > > WARN [CompactionExecutor:6933] 2016-08-08 22:48:11,075 > ViewBuilder.java:178 - Materialized View failed to complete, sleeping 5 > minutes before restarting > java.lang.IllegalArgumentException: Mutation of 17709054 bytes is too > large for the maximum size of 16777216 > > https://gist.github.com/williamsjj/49e4c6a0b3324343205386d040560e1e > > I'm considering bumping commitlog_segment_size_in_mb up to 64MB to get > around this, but it seems like the MV code should be smart enough to stay > under the limit. > > Any advice is greatly appreciated. > > -J >
