cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10256) document commitlog segment size's relationship to max write size
Date Fri, 18 Sep 2015 17:00:06 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14875950#comment-14875950
] 

Aleksey Yeschenko commented on CASSANDRA-10256:
-----------------------------------------------

In addition to that, CASSANDRA-6230 made it possible to explicitly set max mutation size in
cassandra.yaml (by default set to hald the segment size, as it is now).

> 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)

Mime
View raw message