Would be glad to be of any help; it's kind of annoying. * Nothing unusual on any nodes that I can see * Cannot reproduce on a single-node cluster; I see it only on our prod cluster which was running 0.6.13 until this point (cluster conf is attached to the JIRA issue mentioned below).
Let me know of anything that I can try, short of taking my production cluster offline :-P /Janne On Dec 2, 2011, at 20:42 , Jonathan Ellis wrote: > The first step towards determining how serious it is, is showing us > how to reproduce it or otherwise narrowing down what could be causing > it, because timeouts can be caused by a lot of non-bug scenarios. > Does it occur for every query or just some? Is there anything unusual > on the coordinator or replica nodes, like high CPU? Can you reproduce > with the stress tool? Can you reproduce on a single-node-cluster? > That kind of thing. > > On Fri, Dec 2, 2011 at 12:18 PM, Pierre Belanger > <pierre.belan...@xobni.com> wrote: >> Hello, >> >> Is this bug serious enough for 1.0.6 to come out shortly or not? >> >> Thank you, >> PBR >> >> >> >> On Thu, Dec 1, 2011 at 6:05 PM, Zhong Li <z...@voxeo.com> wrote: >>> >>> After upgrade to 1.0.5 RangeSlice got timeout. Ticket >>> https://issues.apache.org/jira/browse/CASSANDRA-3551 >>> >>> On Dec 1, 2011, at 5:43 PM, Evgeniy Ryabitskiy wrote: >>> >>>> +1 >>>> After upgrade to 1.0.5 also have Timeout exception on Secondary Index >>>> search (get_indexed_slices API) . >>> >> > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com
