My guess? 8-10 weeks.
On Fri, Jun 18, 2010 at 1:31 PM, James Golick wrote:
> What's the current timeframe on 0.7?
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com
e-
> > From: "Benjamin Black"
> > 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 histo
Perfect, ship it.
On Fri, Jun 18, 2010 at 10:37 AM, Stu Hood wrote:
> See https://issues.apache.org/jira/browse/CASSANDRA-981
>
> -Original Message-
> From: "Benjamin Black"
> Sent: Friday, June 18, 2010 12:32pm
> To: user@cassandra.apache.org
> Subje
See https://issues.apache.org/jira/browse/CASSANDRA-981
-Original Message-
From: "Benjamin Black"
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 n
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 wrote:
> Our cassandra client fails over if a node times out. Aside from actual
> failure, repair and major compactions can make a node
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
