There are other threads linked to this issue. Most notable, I think we're
hitting
https://issues.apache.org/jira/browse/CASSANDRA-1014
here.
2010/4/27 Schubert Zhang
> Seems:
>
> ROW-MUTATION-STAGE 32 3349 63897493
> is the clue, too many mutation requests are pending.
>
>
> Yes,
Seems:
ROW-MUTATION-STAGE 32 3349 63897493
is the clue, too many mutation requests are pending.
Yes, I also think cassandra should add a mechanism to avoid too many
requests pending (in queue).
When the queue is full, just reject the request from client.
Seems https://issues.apache.
I wrote a script to record the tpstats output every 5 seconds.
Here is the output just before the jvm OOM:
Pool NameActive Pending Completed
FILEUTILS-DELETE-POOL 0 0280
STREAM-STAGE 0 0 0
RESPONSE
I'll work on doing more tests around this. In 0.5 we used a different data
structure that required polling. But this does seem problematic.
-Chris
On Apr 26, 2010, at 7:04 PM, Eric Yu wrote:
> I have the same problem here, and I analysised the hprof file with mat, as
> you said, LinkedBlockQu
I have the same problem here, and I analysised the hprof file with mat, as
you said, LinkedBlockQueue used 2.6GB.
I think the ThreadPool of cassandra should limit the queue size.
cassandra 0.6.1
java version
$ java -version
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b
Thanks Chris
2010/4/26 Chris Goffinet
> Upgrade to b20 of Sun's version of JVM. This OOM might be related to
> LinkedBlockQueue issues that were fixed.
>
> -Chris
>
>
> 2010/4/26 Roland Hänel
>
>> Cassandra Version 0.6.1
>> OpenJDK Server VM (build 14.0-b16, mixed mode)
>> Import speed is about
Upgrade to b20 of Sun's version of JVM. This OOM might be related to
LinkedBlockQueue issues that were fixed.
-Chris
2010/4/26 Roland Hänel
> Cassandra Version 0.6.1
> OpenJDK Server VM (build 14.0-b16, mixed mode)
> Import speed is about 10MB/s for the full cluster; if a compaction is going
>
Cassandra Version 0.6.1
OpenJDK Server VM (build 14.0-b16, mixed mode)
Import speed is about 10MB/s for the full cluster; if a compaction is going
on the individual node is I/O limited
tpstats: caught me, didn't know this. I will set up a test and try to catch
a node during the critical time.
Than
Which version of Cassandra?
Which version of Java JVM are you using?
What do your I/O stats look like when bulk importing?
When you run `nodeprobe -host tpstats` is any thread pool backing up
during the import?
-Chris
2010/4/26 Roland Hänel
> I have a cluster of 5 machines building a Cass
I have a cluster of 5 machines building a Cassandra datastore, and I load
bulk data into this using the Java Thrift API. The first ~250GB runs fine,
then, one of the nodes starts to throw OutOfMemory exceptions. I'm not using
and row or index caches, and since I only have 5 CF's and some 2,5 GB of
10 matches
Mail list logo
