Have you tried lowering the batch size and increasing the time out? Even just to get it to work.
If you get a TimedOutException it means CL number of servers did not respond in time. Cheers ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 28/02/2012, at 8:18 PM, Patrik Modesto wrote: > Hi aaron, > > this is our current settings: > > <property> > <name>cassandra.range.batch.size</name> > <value>1024</value> > </property> > > <property> > <name>cassandra.input.split.size</name> > <value>16384</value> > </property> > > rpc_timeout_in_ms: 30000 > > Regards, > P. > > On Mon, Feb 27, 2012 at 21:54, aaron morton <aa...@thelastpickle.com> wrote: >> What settings do you have for cassandra.range.batch.size >> and rpc_timeout_in_ms ? Have you tried reducing the first and/or increasing >> the second ? >> >> Cheers >> >> ----------------- >> Aaron Morton >> Freelance Developer >> @aaronmorton >> http://www.thelastpickle.com >> >> On 27/02/2012, at 8:02 PM, Patrik Modesto wrote: >> >> On Sun, Feb 26, 2012 at 04:25, Edward Capriolo <edlinuxg...@gmail.com> >> wrote: >> >> Did you see the notes here? >> >> >> I'm not sure what do you mean by the notes? >> >> I'm using the mapred.* settings suggested there: >> >> <property> >> <name>mapred.max.tracker.failures</name> >> <value>20</value> >> </property> >> <property> >> <name>mapred.map.max.attempts</name> >> <value>20</value> >> </property> >> <property> >> <name>mapred.reduce.max.attempts</name> >> <value>20</value> >> </property> >> >> But I still see the timeouts that I haven't with cassandra-all 0.8.7. >> >> P. >> >> http://wiki.apache.org/cassandra/HadoopSupport#Troubleshooting >> >>
