I agree with Rob. You shouldn't need to change the read timeout. We had similar issues with intermittent ReadTimeoutExceptions for a while when we ran Cassandra on underpowered nodes on AWS. We've also seen them when executing unconstrained queries with very large ResultSets (because it takes longer than the timeout to return results). If you can share more details about the hardware environment you are running your cluster on, there are many on the list who can tell you if they are underpowered or not (CPUs, memory, and disk/storage config are all important factors).
You might also try running a newer version of the Java Driver (the later 2.0.x drivers should all work with Cassandra 2.0.3), and I would also suggest moving to a newer (2.0.x) version of Cassandra if you have the option to do so. We had to move to Cassandra 2.0.5 some time ago from 2.0.3 for an issue unrelated to the read timeouts. Steve On Thu, Jan 22, 2015 at 4:48 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Thu, Jan 22, 2015 at 4:19 PM, Asit KAUSHIK <asitkaushikno...@gmail.com> > wrote: > >> There are some values for read timeout in Cassandra.yaml file and the >> default value is 30000 ms change to a bigger value and that resolved our >> issue. >> > Having to increase this value is often a strong signal you are Doing It > Wrong. FWIW! > > =Rob > >
