cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: [RELEASE] Apache Cassandra 1.0.5 released
Date Fri, 02 Dec 2011 18:42:13 GMT
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.belanger@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 <zli@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

Mime
View raw message