ot;,
> and see if things are roughly the same across all the nodes. You could
> also just be under capacity, but more likely, there's an actual
> problem looming somewhere.
>
> Cheers!
> -Matt
>
> On Sat, Mar 23, 2013 at 3:18 AM, wrote:
>
> You can try to disabl
rgram, it tells you more about
> the number of SSTable involved and read/write latency. Somtimes average
> doesn't tell you the whole storey.
> Also check your nodetool tpstats, are there a lot dropped reads?
>
> -Wei
> - Original Message -
> From: "Jon Scarboroug
gt;
> Are your Keys spread across all SSTables ? That will cause every sstable
> read which will increase the I/O.
>
> What compaction are you using ?
>
> From: zod...@fifth-aeon.net<mailto:zod...@fifth-aeon.net> [mailto:
> zod...@fifth-aeon.net] On Behalf Of Jon Scarboroug
Hello,
We've had a 5-node C* cluster (version 1.1.0) running for several months.
Up until now we've mostly been writing data, but now we're starting to
service more read traffic. We're seeing far more disk I/O to service these
reads than I would have anticipated.
The CF being queried consists of