Re: Handling failures in Thrift

2010-05-13 Thread Ian Soboroff
I suspect the issue in my case is saturation, or that the node has gone down. In the case of saturation, sleeping and retrying seems to be the fix. Otherwise setup a new transport/proto/client to a new host in the cluster. Ok, got it. Ian On Thu, May 13, 2010 at 2:20 PM, Roger Schildmeijer wrot

Re: Handling failures in Thrift

2010-05-13 Thread Roger Schildmeijer
All the Exceptions are documented on the API page (http://wiki.apache.org/cassandra/API) on the wiki. * UnavailableException -- "Not all the replicas required could be created and/or read." * TimedOutException -- "The node responsible for the write or read did not respond during the rpc interva