Thank you for your reply Do you know if there are documentation of hector I can read to understand this behavior?
Thanks Michael -----Original Message----- From: sc...@scode.org [mailto:sc...@scode.org] On Behalf Of Peter Schuller Sent: Monday, January 09, 2012 5:29 PM To: dev@cassandra.apache.org Subject: Re: Using quorum to read data > 2012-01-09 11:58:33,325 WARN > [me.prettyprint.cassandra.connection.CassandraHostRetryService] - <Downed > 192.168.80.31(192.168.80.31):9160 host still appears to be down: Unable to > open transport to 192.168.80.31(192.168.80.31):9160 , > java.net.ConnectException: Connection refused: connect> > > What am I missing? That's not a timeout, but a failure to connect. Did you give Hector all of the nodes in the cluster or enable auto-discovery? If the above is the only error you see, it seems likely that you just need to configure your client to talk to the entire cluster. (I don't remember off hand how to tell hector to use auto-discovery.) -- / Peter Schuller (@scode, http://worldmodscode.wordpress.com)