[
https://issues.apache.org/jira/browse/CASSANDRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757799#action_12757799
]
Chris Goffinet commented on CASSANDRA-433:
------------------------------------------
As per discussion with jbellis, I agree this is the right way going forward.
You will want to increase the Memtable threshold and object sizes when doing
Binary Memtable import, which also would most likely yield increasing the heap
size. But once done, you will not want to have these thresholds that high at
all times. So since you are decreasing the heap, this makes sense. This might
cause a little difficulty with op situations but we will be providing a way to
change these thresholds/sizes using either nodeprobe or another utility.
> 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: Chris Goffinet
> Fix For: 0.5
>
> Attachments:
> 0001-CASSANDRA-433.-Consolidated-BMT-threshold-and-object.patch,
> 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.
