[
https://issues.apache.org/jira/browse/CASSANDRA-10256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876845#comment-14876845
]
Chris Gerlt commented on CASSANDRA-10256:
-----------------------------------------
Since the code has:
MAX_MUTATION_SIZE = DatabaseDescriptor.getCommitLogSegmentSize()
The MAX_MUTATION_SIZE equals the commitlog segment size
Note: commitlog_segment_size_in_mb = 32 (by default). Also,
commitlog_segment_size_in_mb*1024*1024 is the commit log segment size in bytes
(Hope this helps and if anything is wrong please correct)
> document commitlog segment size's relationship to max write size
> ----------------------------------------------------------------
>
> Key: CASSANDRA-10256
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10256
> Project: Cassandra
> Issue Type: Improvement
> Components: Config
> Reporter: Chris Burroughs
> Priority: Trivial
> Labels: lhf
>
> This is in the code:
> https://github.com/apache/cassandra/blob/cassandra-2.1/src/java/org/apache/cassandra/db/commitlog/CommitLog.java#L57
> But not part of the description in cassandra.yaml
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
