[
https://issues.apache.org/jira/browse/CASSANDRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-433:
-------------------------------------
Attachment: 433.patch
from irc:
jbellis: if you really use different sizes for BMt and normal Mt then i think
we should have different settings. i'm just not sure why you'd want to do that
goffinet: we wouldnt want it to run that high [a heap] at all times; we'd
rather use the ram for FS cache
jbellis: so if you do want different sizes for Mt/BMt let's just leave the
separate BMt setting in and not make ops have to mess with things when bulk
load is done
goffinet: ok
here is patch.
> 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, 433.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.
