Ninad, > Here's a bit more information: > > -Few rows in this column family can grow quite wide (> 100K columns) > > -But we keep seeing this behavior most frequently with rows with just 1 or > two columns . The typical behavior is: Machine A adds a new row and a column. > 30-60 seconds later Machine B tries to read this row. It doesn't find the > row. So the application retries within 500ms. This time it finds the row.
You wrote a lot of useful info in your original post, sorry I missed it in my first reply. Only thing there that stands out, apart from short reads that Jeff's already pointed out, is the use of `speculative_retry='ALWAYS'`. Has there topology changes in your cluster recently? Next step would be to try and repeat it with tracing. regards, Mick -- Mick Semb Wever Australia The Last Pickle Apache Cassandra Consulting http://www.thelastpickle.com --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
