Absolutely right! Thanks, fixed for 0.7.4.
On Fri, Mar 11, 2011 at 4:14 PM, Erik Forkalsrud wrote:
> On 03/11/2011 12:13 PM, Jonathan Ellis wrote:
>>
>> https://issues.apache.org/jira/browse/CASSANDRA-2158, fixed in 0.7.3
>>
>> you could have saved a lot of time just by upgrading first. :)
>
>
>
On 03/11/2011 12:13 PM, Jonathan Ellis wrote:
https://issues.apache.org/jira/browse/CASSANDRA-2158, fixed in 0.7.3
you could have saved a lot of time just by upgrading first. :)
It looks like the fix isn't entirely correct. The bug is still in
0.7.3. In Memtable.java, the line:
THRES
On 03/11/2011 12:13 PM, Jonathan Ellis wrote:
https://issues.apache.org/jira/browse/CASSANDRA-2158, fixed in 0.7.3
you could have saved a lot of time just by upgrading first. :)
Hmm, I'm testing with 0.7.3 ...
but now I know at least which knob to turn.
- Erik -
https://issues.apache.org/jira/browse/CASSANDRA-2158, fixed in 0.7.3
you could have saved a lot of time just by upgrading first. :)
On Fri, Mar 11, 2011 at 2:02 PM, Erik Forkalsrud wrote:
> On 03/11/2011 04:56 AM, Zhu Han wrote:
>>
>> When I run it on my laptop (Fedora 14, 64-bit, 4 cores, 8GB R
On 03/11/2011 04:56 AM, Zhu Han wrote:
When I run it on my laptop (Fedora 14, 64-bit, 4 cores, 8GB RAM)
it flushes one Memtable with 5000 operations
When I run it on a server (RHEL5, 64-bit, 16 cores, 96GB RAM) it
flushes 100 Memtables with anywhere between 1 operation and 359
On Fri, Mar 11, 2011 at 10:40 AM, Erik Forkalsrud wrote:
>
> I see the same behavior with smaller batch sizes. It appears to happen
> when starting Cassandra with the defaults on relatively large systems.
> Attached is a script I created to reproduce the problem. (usage: mutate.sh
> /path/to/ap
Thus if needed I can debug the code but I would need some input from
your team.
Ignace
-Original Message-
From: Ryan King [mailto:r...@twitter.com]
Sent: donderdag 10 maart 2011 18:18
To: user@cassandra.apache.org
Cc: Desimpel, Ignace
Subject: Re: FW: Very slow batch insert using ve
I see the same behavior with smaller batch sizes. It appears to happen
when starting Cassandra with the defaults on relatively large systems.
Attached is a script I created to reproduce the problem. (usage:
mutate.sh /path/to/apache-cassandra-0.7.3-bin.tar.gz) It extracts a
stock cassand
Why use such a large batch size?
-ryan
On Thu, Mar 10, 2011 at 6:31 AM, Desimpel, Ignace
wrote:
>
>
> Hello,
>
> I had a demo application with embedded cassandra version 0.6.x, inserting
> about 120 K row mutations in one call.
>
> In version 0.6.x that usually took about 5 seconds, and I could
