Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Cassandra error: Too large commit log size

Updated on July 5, 2022

This content applies only to On-premises and Client-managed cloud environments

Cassandra logs display the following error: java.lang.IllegalArgumentException: Mutation of number-value bytes is too large for the maximum size of number-value.


When the Cassandra commit log takes up too much disk space, connection issues might occur. The following is an example of an error message for this issue: java.lang.IllegalArgumentException: Mutation of 33749684 bytes is too large for the maximum size of 33554432.

  • Review your application data model and segment the records into smaller units.
    For example: If your main data set contains 2,000 customer records, segment the data set into four smaller data sets of 500 customer records each.
  • As a temporary workaround for the error, in the prconfig.xml file, increase the maximum commit log size in megabytes by specifying the value of the commitlog_segment_size_in_mb property.
    The default maximum commit log size is 32 megabytes.

    For more information, see Changing node settings by modifying the prconfig.xml file.

    For example: <env name=“dnode/yaml/commitlog_segment_size_in_mb” value=“64”/>
    Increase the maximum commit log size only as a temporary workaround. Permanently increased record writes might have a negative impact on database performance, which can affect system performance.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us