[
https://issues.apache.org/jira/browse/CASSANDRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753728#action_12753728
]
Jonathan Ellis commented on CASSANDRA-433:
------------------------------------------
50k is ridiculously small, but the reason you need 2 checks is, the size
estimate isn't even close to correct for small rows.
should we just make BMt use the memtable size and object count settings instead
of making Binary versions of each in the config file?
I can't think of a reason to want to have separate settings for these, since if
you are using both normal Mt and BMt at the same time you are Doing It Wrong. :)
> Remove item flush limit in BinaryMemtable
> -----------------------------------------
>
> Key: CASSANDRA-433
> URL: https://issues.apache.org/jira/browse/CASSANDRA-433
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.5
> Reporter: Johan Oskarsson
> Assignee: Johan Oskarsson
> Fix For: 0.5
>
> Attachments: CASSANDRA-433.patch
>
>
> The BinaryMemtable flushes in memory data to disk when the size of the data
> reaches a certain limit. There is also a hard coded limit that initiates the
> flush when more then 50000 items have been inserted. That causes issues if a
> lot of small items are inserted, we should remove or make the limit
> configurable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
