Does a later query on the same ID also behave poorly? (Or perhaps it gets
cached and is fast the next time…) My first thought was that perhaps the slow
records had many updates that were being read (or tombstones being read over)
to assemble the record. A trace on the query with that key might r
check for level 2 (stop the world) garbage collections.
*...*
*Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872*
On Fri, Mar 17, 2017 at 11:51 AM, Chuck Reynolds
wrote:
> I have a large Cassandra 2.1.13 ring (60 nodes) in AWS that has
> consistently random high r
Probably Jvm pauses. Check your logs for long GC times.
On Fri, Mar 17, 2017 at 11:51 AM Chuck Reynolds
wrote:
> I have a large Cassandra 2.1.13 ring (60 nodes) in AWS that has
> consistently random high read times. In general most reads are under 10
> milliseconds but with in the 30 request the
