It's known that compaction hurts the node performance so that it might
miss some requests. That's why it's important to handle these
situations and the client needs to retry the operation into another
working host. We have been storing performance data from each
cassandra request which we do into
On 21-09-2010 15:29, Juho Mäkinen wrote:
It's known that compaction hurts the node performance so that it might
miss some requests. That's why it's important to handle these
situations and the client needs to retry the operation into another
working host. We have been storing performance data
The standard thrift php client detects the problem by normal timeout
which triggers a TException (Thrift Exception) which indicates that
request timeouted, or the (in)famous timed out reading 4 bytes from
host. These errors are catched on my php wrapper
On Tue, Sep 21, 2010 at 8:29 AM, Juho Mäkinen juho.maki...@gmail.comwrote:
It's known that compaction hurts the node performance so that it might
miss some requests. That's why it's important to handle these
situations and the client needs to retry the operation into another
working host. We
Thanks for this, really interesting stuff.Just to make sure I'munderstandingit, this is for PHP clients witha 1 second timeout and retry is to a differentnode in the cluster with the same timeout.Have you enabled the Dynamic Snitch ?http://www.riptano.com/blog/whats-new-cassandra-065AaronOn 22
