incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Golick <jamesgol...@gmail.com>
Subject Re: Failover and slow nodes
Date Fri, 18 Jun 2010 20:31:34 GMT
What's the current timeframe on 0.7?

On Fri, Jun 18, 2010 at 1:45 PM, Benjamin Black <b@b3k.us> wrote:

> Perfect, ship it.
>
> On Fri, Jun 18, 2010 at 10:37 AM, Stu Hood <stu.hood@rackspace.com> wrote:
> > See https://issues.apache.org/jira/browse/CASSANDRA-981
> >
> > -----Original Message-----
> > From: "Benjamin Black" <b@b3k.us>
> > Sent: Friday, June 18, 2010 12:32pm
> > To: user@cassandra.apache.org
> > Subject: Re: Failover and slow nodes
> >
> > Would be interesting to have a snitch that manipulated responses for
> > read nodes based on historical response times.
> >
> > On Fri, Jun 18, 2010 at 8:21 AM, James Golick <jamesgolick@gmail.com>
> wrote:
> >> Our cassandra client fails over if a node times out. Aside from actual
> >> failure, repair and major compactions can make a node so slow that it
> >> affects application performance.
> >> One problem we've run in to is that a node in the midst of repair will
> still
> >> have requests routed to it internally, even if all clients have failed
> over.
> >> With a small number of nodes, this has a major impact on the performance
> of
> >> the overall system.
> >> I'm wondering whether people have any recommendations on tuning this
> >> behaviour. It would be really nice not to route requests to an insanely
> slow
> >> node.
> >
> >
> >
>

Mime
View raw message