: Friday, March 17, 2017 2:51 PM
To: user@cassandra.apache.org
Subject: Random slow read times in Cassandra
I have a large Cassandra 2.1.13 ring (60 nodes) in AWS that has consistently
random high read times. In general most reads are under 10 milliseconds but
with in the 30 request there is usually a
check for level 2 (stop the world) garbage collections.
*...*
*Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872*
On Fri, Mar 17, 2017 at 11:51 AM, Chuck Reynolds
wrote:
> I have a large Cassandra 2.1.13 ring (60 nodes) in AWS that has
> consistently random high r
Probably Jvm pauses. Check your logs for long GC times.
On Fri, Mar 17, 2017 at 11:51 AM Chuck Reynolds
wrote:
> I have a large Cassandra 2.1.13 ring (60 nodes) in AWS that has
> consistently random high read times. In general most reads are under 10
> milliseconds but with in the 30 request the
I have a large Cassandra 2.1.13 ring (60 nodes) in AWS that has consistently
random high read times. In general most reads are under 10 milliseconds but
with in the 30 request there is usually a read time that is a couple of seconds.
Instance type: r4.8xlarge
EBS GP2 volumes, 3tb with 9000 IOPS
> I have a slow query that is making me think I don't understand the data
model for
> time series:
> select asset, returns from marketData where date >= 20130101 and date <=
20130110
> allow filtering;
>
> create table marketData {
> asset varchar,
> returns double,
> date timestamp,
> PRIMARY KEY(
I have a slow query that is making me think I don't understand the data model
for
time series:
select asset, returns from marketData where date >= 20130101 and date <=
20130110
allow filtering;
create table marketData {
asset varchar,
returns double,
date timestamp,
PRIMARY KEY(asset, date) }
2012/3/5 Jeesoo Shin
> Thank you for reply. :)
> Yes I did multiple thread.
> 160, 320 gave me same result.
>
> On 3/5/12, ruslan usifov wrote:
> > 2012/3/5 Jeesoo Shin
> >
> >> Hi all.
> >>
> >> I have very SLOW READ here. :-(
>
And sum of all rq/s threads is 160??
2012/3/5 Jeesoo Shin
> Thank you for reply. :)
> Yes I did multiple thread.
> 160, 320 gave me same result.
>
> On 3/5/12, ruslan usifov wrote:
> > 2012/3/5 Jeesoo Shin
> >
> >> Hi all.
> >>
> >> I ha
Thank you for reply. :)
Yes I did multiple thread.
160, 320 gave me same result.
On 3/5/12, ruslan usifov wrote:
> 2012/3/5 Jeesoo Shin
>
>> Hi all.
>>
>> I have very SLOW READ here. :-(
>> I made a cluster with three node (aws xlarge, replication = 3)
>>
2012/3/5 Jeesoo Shin
> Hi all.
>
> I have very SLOW READ here. :-(
> I made a cluster with three node (aws xlarge, replication = 3)
> Cassandra version is 1.0.6
> I have inserted 1,000,000 rows. (standard column)
> Each row has 200 columns.
> Each column has 16 byte key
Hi all.
I have very SLOW READ here. :-(
I made a cluster with three node (aws xlarge, replication = 3)
Cassandra version is 1.0.6
I have inserted 1,000,000 rows. (standard column)
Each row has 200 columns.
Each column has 16 byte key, 512 byte value.
I used Hector createSliceQuery to get one
:jbel...@gmail.com]
Sent: Thursday, April 08, 2010 10:12 AM
To: user@cassandra.apache.org
Subject: Re: Some insight into the slow read speed. Where to go from here? RC1
MESSAGE-DESERIALIZER-POOL
Have you checked iostat -x ?
On Thu, Apr 8, 2010 at 9:45 AM, Mark Jones wrote:
> I don't s
The tooth wave in memory utilization could be memtable dumps. I/O wait in
TCP happens when you are overwhelming the server with requests. Could you
run sar and find out how many bytes/sec you are receiving/transmitting?
Cheers
Avinash
On Thu, Apr 8, 2010 at 7:45 AM, Mark Jones wrote:
> I don't
The sawtooth ram graph is typical of normal GC activity, btw -- the GC
doesn't bother with a major collection until it reaches some percent
of the total available.
Have you checked iostat -x ?
On Thu, Apr 8, 2010 at 9:45 AM, Mark Jones wrote:
> I don't see any way to increase the # of active Deserializers in
> storage-conf.xml
>
> Tpstats more than 8 hours after insert/read stop
>
> Pool Name Active Pending Completed
> FILEUTILS-D
I don't see any way to increase the # of active Deserializers in
storage-conf.xml
Tpstats more than 8 hours after insert/read stop
Pool NameActive Pending Completed
FILEUTILS-DELETE-POOL 0 0227
STREAM-STAGE 0
16 matches
Mail list logo
