[
https://issues.apache.org/jira/browse/CASSANDRA-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873115#action_12873115
]
Toby Jungen commented on CASSANDRA-1093:
----------------------------------------
I've been able to observe the error with a generate parameter of 25,000. Note
that the generate step creates the entire randomized data set in memory before
writing it to disk, so this test is limited by memory. With a parameter of
25,000 I ran fine with 512MB of heap space, at 100,000 I'd expect you to need
around 2GB of heap space.
The parameter for the generate step corresponds to a "document", and each
document results in roughly 100 rows.
> BinaryMemtable interface silently dropping data.
> ------------------------------------------------
>
> Key: CASSANDRA-1093
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1093
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Linux Centos5, Fedora Core 4. Java HotSpot Server
> 1.6.0_14. See readme for more details.
> Reporter: Toby Jungen
> Assignee: Brandon Williams
> Fix For: 0.6.3
>
> Attachments: cassandra_bmt_test.tar.gz
>
>
> I've been attempting to use the Binary Memtable (BMT) interface to load a
> large number of rows. During my testing, I discovered that on larger loads
> (~1 million rows), occasionally some of the data never appears in the
> database. This happens in a non-deterministic manner, as sometimes all the
> data loads fine, and other times a significant chunk goes missing. No errors
> are ever logged to indicate a problem. I'm attaching some sample code that
> approximates my application's usage of Cassandra and explains this bug in
> more detail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
