Hi:
These days I found my Cassandra is strange, much slower than before. And
I Spent much time to figure it out and today I got the answer.
Some bad buy keeps on writing many data day and night, then made a very big
row mutation which size is about 140M.
In this period I restarted some
much slower than message de-serialization and costs many
milliseconds, so It look like that MESSAGE-DESERIALIZER-POOL is slow down by
SliceFromReadCommand.
From: Lu Ming
Sent: Wednesday, June 23, 2010 11:50 PM
To: user@cassandra.apache.org
Subject: MESSAGE-DESERIALIZER-POOL is slow down by
Yesterday and today , I found there are many pending message (>100,000) to be
de-serialized in MESSAGE-DESERIALIZER-POOL.
and I do the thread dump, It seems that some "SliceRead" is NOT executed by
StageManager.READ_STAGE and executed by MESSAGE-DESERIALIZER-POOL.
It is somewhat strange. Read fr
Many files are corrupted when our cassandra is update to 0.6.2
COMPACTION-POOL is down caused by the following error.
and some nodes can NOT startup because of this error.
Is it caused by the issue CASSANDRA-1169? The node got the wrong or corrupted
stream file?
ERROR [COMPACTION-POOL:1] 2010-06
For hard disk drives, the random IOPS numbers are primarily dependent on the
storage device's random seek time.
7200RPM SATA drives - ~90 IOPS[citation needed]
10kRPM Serial Attached SCSI drives - ~ 140 IOPS[citation needed]
15kRPM Serial Attached SCSI drives - ~180 IOPS[citation needed]
Intel X2
our cassandra cluster is delpoyed in two datacenters.
--
From: "Lu Ming"
Sent: Friday, June 04, 2010 7:01 PM
To:
Subject: Re: High CPU Usage since 0.6.2
I do the Thread Dump on each cassandra node, and count the thread with
call sta
n.run" occupies the 100% CPU
So I guess the code in IncomingTcpConnection.java:66 cause high CPU usage.
if (isStream)
{
new IncomingStreamReader(socket.getChannel()).read();
}
------
-
From: "Chris Goffinet"
Sent: Friday, June 04, 2010 1:50 PM
To:
Cc:
Subject: Re: High CPU Usage since 0.6.2
We're seeing this as well. We were testing with a 40+ node cluster on the
latest 0.6 branch from few days ago.
-Chris
On Jun 3, 2010, at 9:55 PM, Lu Mi
I have ten 0.5.1 Cassandra nodes in my cluster, and I update them to
cassandra to 0.6.2 yesterday.
But today I find six cassandra nodes have high CPU usage more than 400% in
my 8-core CPU sever.
The worst one is more than 760%. It is very serious.
I use jvisualvm to watch the worst node, and
Cheers!
From: Donyee
Sent: Tuesday, April 13, 2010 11:10 PM
To: user@cassandra.apache.org
Subject: Re: [RELEASE] 0.6.0
Great!
2010/4/13 Eric Evans
I'm pleased to announce the official release of Apache Cassandra 0.6.0,
(aka The Best Evar). Get yours now from the usual place[1], and a
10 matches
Mail list logo
