Hey,
We had this one, even tho in the hector documentation it says that it
retry s failed servers even 30 by default, it doesn't.
Once we explicitly set it to X seconds, when ever there is a failure,
ie with network (AWS), it will retry and add it back into the pool.
Ben
On 11 October 2011 11:0
603)
at java.lang.Thread.run(Thread.java:636)
On 5 October 2011 20:03, Ben Ashton wrote:
> Ah thats great!
>
> I was rubbing my head for a while as google only showed mailing lists
> posts with the same error.
>
> All working now, thanks
>
> On 5 October 2011 19:49
Ah thats great!
I was rubbing my head for a while as google only showed mailing lists
posts with the same error.
All working now, thanks
On 5 October 2011 19:49, Jonathan Ellis wrote:
> Did you try wiki.apache.org/cassandra/FAQ#schema_disagreement ?
>
> On Wed, Oct 5, 2011 at 1:4
Hi Guys,
How would I go about fixing this? (running 0.8.4)
[default@unknown] connect 10.58.135.19/9160;
Connected to: "Test Cluster" on 10.58.135.19/9160
[default@unknown] describe cluster;
Cluster Information:
Snitch: org.apache.cassandra.locator.SimpleSnitch
Partitioner: org.apache.cassan
Hi Guys,
I have our multi DC setup running on EC2.
Latency on the connections between the servers is <2ms, monitored
writes are ~3-4ms, reads are 50 to 2200 ms, normally ~80ms
Is this normal? I know there are some optimisation java guys can do
with hector, but is there anything I can do on a sys
the property file snitch?
>
> On Sep 3, 2011, at 5:09 PM, Ben Ashton wrote:
>
> > I've been dropped in it a little and had to build a prod setup going live
> on monday.
> >
> > At the moment I have setup three server in EC2 US, one each AZ
> >
> > the
I've been dropped in it a little and had to build a prod setup going live on
monday.
At the moment I have setup three server in EC2 US, one each AZ
the servers are setup as follows:-
m1.xlarge using the Amazons AMI instance storage image, the ephemerals 4 x
420 GB setup in raid10 and formatted w
