cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Soboroff <isobor...@gmail.com>
Subject Re: Scaling problems
Date Sun, 23 May 2010 02:07:03 GMT
I'll try this.  HH backs up because nodes are failing.  I haven't read the
code, but why should HH suck CPU?  As I understand it, there's nothing to
hand off until the destination comes back up, and Gossip should tell us
that, no?  In the interim, it's just a cache of writes waiting to be sent.

Is there some way to tell the system "Just stop caring, I'm just writing,
let's worry about leveling out when I get around to wanting to read?"

Ian

On Fri, May 21, 2010 at 9:06 PM, Jonathan Ellis <jbellis@gmail.com> wrote:

> On Fri, May 21, 2010 at 9:09 AM, Ian Soboroff <isoboroff@gmail.com> wrote:
> > HINTED-HANDOFF-POOL               1       158             23
>
> this is your smoking gun.  HH tasks suck a ton of CPU and you have 158
> backed up.
>
> i would just blow the HH files away from your data/system directory,
> restart the node, and run repair (assuming all your other nodes are
> alive again).
>

Mime
View raw message