Bringing together the Apache Cassandra experts from the community and DataStax.

Want to learn? Have a question? Want to share your expertise? You are in the right place!

Not sure where to begin? Getting Started

 

question

mukesh.modi.india_53022 avatar image
mukesh.modi.india_53022 asked Erick Ramirez edited

How does write work in terms of commitlog_segment_size_in_mb?

Hi Team,

We caught the error "Mutation of 17156436 bytes is too large for the maximum size of 16777216" in Cassandra.

I understand, we should increase the commitlog_segment_size_in_mb to 64 mb as mutation usually use 1/2 of commilog_segment_size and we were using 32 mb.

Now, I understand, how commitlog_segment_size_in_mb works.

Is it because the size of writes has increased, or is it because commitlog has increased because the size of writes went high? I mean multiple writes in commitlog or one write request which has more than 16mb of size.

Thanks in advance.

Cheers,

Mukesh kumar

commitlog
10 |1000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

Erick Ramirez avatar image
Erick Ramirez answered

@mukesh.modi.india_53022 you are getting that error because the application is sending a really large write. We do not recommend increasing the commitlog segment size unless you fully understand the implications. Cheers!

Share
10 |1000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.