[
https://issues.apache.org/jira/browse/CASSANDRA-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873139#action_12873139
]
Toby Jungen edited comment on CASSANDRA-1093 at 5/28/10 4:24 PM:
-----------------------------------------------------------------
Looks like everything passed. You may want to re-run from start to finish one
or two more times (my error didn't occur consistently), but if it still passes
at that point then close this issue as CannotReproduce and I'll attribute the
problem to my hardware setup. As mentioned I've found somewhat of a workaround.
I'll gladly donate my test code as a possible unit test for BMT if needed. :)
was (Author: tjungen):
Looks like everything passed. You may want to re-run from start to finish
one or two more times (my error didn't occur consistently), but if it still
passes at that point then close this issue as WontFix and I'll attribute the
problem to my hardware setup. As mentioned I've found somewhat of a workaround.
I'll gladly donate my test code as a possible unit test for BMT if needed. :)
> 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.
