Not sure about that Hector Version, but there was a Hector Bug that Hector did
Not stop using a Dead Node As Proxy and that it did not do proper Load
balancing in the requests. If you enable trace Logs for Hector you can See
which nodes it uses for requests. If there is a newer 0.6 Hector you sh
What is the consistency level you are using ?
And as Ed said, if you can provide the stacktrace that would help too.
On Sat, Apr 9, 2011 at 7:02 PM, aaron morton wrote:
> btw, the nodes are a tad out of balance was that deliberate ?
>
> http://wiki.apache.org/cassandra/Operations#Token_selection
btw, the nodes are a tad out of balance was that deliberate ?
http://wiki.apache.org/cassandra/Operations#Token_selection
http://wiki.apache.org/cassandra/Operations#Load_balancing
Aaron
On 10 Apr 2011, at 08:44, Ed Anuff wrote:
> Sounds like the problem might be on the hector side. Lots of
Sounds like the problem might be on the hector side. Lots of hector
users on this list, but usually not a bad idea to ask on
hector-us...@googlegroups.com (cc'd).
The jetty servers stopping responding is a bit vague, somewhere in
your logs is an error message that should shed some light on where
The hector clients are used as part of our jetty servers. And, the
jetty servers stop responding when one of the Cassandra nodes go down.
Vram
On Sat, Apr 9, 2011 at 11:54 AM, Joe Stump wrote:
> Did the Cassandra cluster go down or did you start getting failures from the
> client when it routed
Did the Cassandra cluster go down or did you start getting failures from the
client when it routed queries to the downed node? The key in the client is to
keep working around the ring if the initial node is down.
--Joe
On Apr 9, 2011, at 12:52 PM, Vram Kouramajian wrote:
> We have a 5 Cassandr
We have a 5 Cassandra nodes with the following configuration:
Casandra Version: 0.6.11
Number of Nodes: 5
Replication Factor: 3
Client: Hector 0.6.0-14
Write Consistency Level: Quorum
Read Consistency Level: Quorum
Ring Topology:
OwnsRange Ring
13275670
