We are using Cassandra 2.0.14 with Hector as client ( will be gradually moving 
to CQL Driver ). 


Often we see that heavy read and write loads lead to Cassandra timeouts and 
unpredictable results due to gc pauses and request timeouts. We need to know 
the best way to throttle read and write load on Cassandra such that even if 
heavy operations are slower they complete gracefully. This will also shield us 
against misbehaving clients.


I was thinking of limiting rpc connections via rpc_max_threads property and 
implementing connection pool at client side. 


I would appreciate if you could please share your suggestions on the above 
mentioned approach or share any alternatives to the approach.


Thanks

Anuj Wadehra


Reply via email to