You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Sylvain Lebresne <sy...@datastax.com> on 2011/11/30 20:10:51 UTC
[RELEASE] Apache Cassandra 1.0.5 released
As indicated in a preceding mail (http://goo.gl/R1r1V), the release of 1.0.4
unfortunately shipped with two important regressions. The Cassandra team is
pleased to announce the release of Apache Cassandra version 1.0.5 that comes
to fix those two issues[1], but is identical to 1.0.4 otherwise.
Cassandra 1.0.5 can be de downloaded in the usual places, i.e:
http://cassandra.apache.org/download/
We sincerely apologize for any inconvenience caused by 1.0.4. As always,
please pay attention to the release notes[2] and Let us know[3] if you were to
encounter any problem.
Have fun!
[1]: http://goo.gl/Fod0B (CHANGES.txt)
[2]: http://goo.gl/gtUvs (NEWS.txt)
[3]: https://issues.apache.org/jira/browse/CASSANDRA
RE: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Michael Vaknine <mi...@citypath.com>.
Thanks,
The files are there already.
-----Original Message-----
From: Brandon Williams [mailto:driftx@gmail.com]
Sent: Wednesday, November 30, 2011 9:43 PM
To: user@cassandra.apache.org
Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
On Wed, Nov 30, 2011 at 1:29 PM, Michael Vaknine <mi...@citypath.com>
wrote:
> The files are not on the site
> The requested URL
/apache//cassandra/1.0.5/apache-cassandra-1.0.5-bin.tar.gz
> was not found on this server.
It takes the mirrors some time to sync.
-Brandon
Re: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Zhong Li <zl...@voxeo.com>.
You may run "stress -d <node>" to create Standard1 CF and data.
On Dec 3, 2011, at 3:44 PM, <mi...@thomsonreuters.com> <mi...@thomsonreuters.com> wrote:
> Hi Zhong Li,
>
> When I used stress tool to test, I got:
>
> Operation [15] retried 10 times - error inserting key 0015 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [37] retried 10 times - error inserting key 0037 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [17] retried 10 times - error inserting key 0017 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [40] retried 10 times - error inserting key 0040 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [28] retried 10 times - error inserting key 0028 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [2] retried 10 times - error inserting key 0002 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [13] retried 10 times - error inserting key 0013 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [29] retried 10 times - error inserting key 0029 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [30] retried 10 times - error inserting key 0030 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [23] retried 10 times - error inserting key 0023 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [21] retried 10 times - error inserting key 0021 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [42] retried 10 times - error inserting key 0042 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [0] retried 10 times - error inserting key 0000 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> Operation [11] retried 10 times - error inserting key 0011 ((InvalidRequestException): unconfigured columnfamily Standard1)
>
> 0,0,0,NaN,0
> END
>
> Do I need to create the column family manually first, or it is created by the stress tool automatically? Why did I get the errors above?
>
> Thanks,
> Mike
>
> -----Original Message-----
> From: Zhong Li [mailto:zli@voxeo.com]
> Sent: Friday, December 02, 2011 3:24 PM
> To: user@cassandra.apache.org
> Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
>
> I just tested with stress tool, it is reproducible and timeout happens always.
>
> ./stress -d <mynode address> -e QUORUM -l 3 -o RANGE_SLICE
> total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
> total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
> 0,0,0,NaN,10
> 0,0,0,NaN,20
> 0,0,0,NaN,30
> 0,0,0,NaN,40
> 0,0,0,NaN,50
> 0,0,0,NaN,60
> 0,0,0,NaN,70
> 0,0,0,NaN,80
> 0,0,0,NaN,91
> 0,0,0,NaN,101
> Operation [2] retried 10 times - error on calling get_indexed_slices for range offset 0000002 ((TimedOutException))
>
> Operation [46] retried 10 times - error on calling get_indexed_slices for range offset 0000046 ((TimedOutException))
>
> Operation [47] retried 10 times - error on calling get_indexed_slices for range offset 0000047 ((TimedOutException))
>
> Operation [24] retried 10 times - error on calling get_indexed_slices for range offset 0000024 ((TimedOutException))
>
> Operation [45] retried 10 times - error on calling get_indexed_slices for range offset 0000045 ((TimedOutException))
>
> Operation [48] retried 10 times - error on calling get_indexed_slices for range offset 0000048 ((TimedOutException))
>
> Operation [5] retried 10 times - error on calling get_indexed_slices for range offset 0000005 ((TimedOutException))
>
> Operation [28] retried 10 times - error on calling get_indexed_slices for range offset 0000028 ((TimedOutException))
>
> Operation [0] retried 10 times - error on calling get_indexed_slices for range offset 0000000 ((TimedOutException))
>
> Operation [23] retried 10 times - error on calling get_indexed_slices for range offset 0000023 ((TimedOutException))
>
> Operation [32] retried 10 times - error on calling get_indexed_slices for range offset 0000032 ((TimedOutException))
>
> Operation [36] retried 10 times - error on calling get_indexed_slices for range offset 0000036 ((TimedOutException))
>
> Operation [16] retried 10 times - error on calling get_indexed_slices for range offset 0000016 ((TimedOutException))
>
> Operation [6] retried 10 times - error on calling get_indexed_slices for range offset 0000006 ((TimedOutException))
>
> Operation [9] retried 10 times - error on calling get_indexed_slices for range offset 0000009 ((TimedOutException))
>
> Operation [11] retried 10 times - error on calling get_indexed_slices for range offset 0000011 ((TimedOutException))
>
> Operation [25] retried 10 times - error on calling get_indexed_slices for range offset 0000025 ((TimedOutException))
>
> Operation [26] retried 10 times - error on calling get_indexed_slices for range offset 0000026 ((TimedOutException))
>
> Operation [43] retried 10 times - error on calling get_indexed_slices for range offset 0000043 ((TimedOutException))
>
> Operation [27] retried 10 times - error on calling get_indexed_slices for range offset 0000027 ((TimedOutException))
>
> Operation [33] retried 10 times - error on calling get_indexed_slices for range offset 0000033 ((TimedOutException))
>
> Operation [44] retried 10 times - error on calling get_indexed_slices for range offset 0000044 ((TimedOutException))
>
> Operation [19] retried 10 times - error on calling get_indexed_slices for range offset 0000019 ((TimedOutException))
>
> Operation [35] retried 10 times - error on calling get_indexed_slices for range offset 0000035 ((TimedOutException))
>
> Operation [34] retried 10 times - error on calling get_indexed_slices for range offset 0000034 ((TimedOutException))
>
> Operation [30] retried 10 times - error on calling get_indexed_slices for range offset 0000030 ((TimedOutException))
>
> Operation [14] retried 10 times - error on calling get_indexed_slices for range offset 0000014 ((TimedOutException))
>
> Operation [7] retried 10 times - error on calling get_indexed_slices for range offset 0000007 ((TimedOutException))
>
> Operation [20] retried 10 times - error on calling get_indexed_slices for range offset 0000020 ((TimedOutException))
>
> Operation [3] retried 10 times - error on calling get_indexed_slices for range offset 0000003 ((TimedOutException))
>
> Operation [8] retried 10 times - error on calling get_indexed_slices for range offset 0000008 ((TimedOutException))
>
> Operation [15] retried 10 times - error on calling get_indexed_slices for range offset 0000015 ((TimedOutException))
>
> Operation [29] retried 10 times - error on calling get_indexed_slices for range offset 0000029 ((TimedOutException))
>
> Operation [12] retried 10 times - error on calling get_indexed_slices for range offset 0000012 ((TimedOutException))
>
> Operation [40] retried 10 times - error on calling get_indexed_slices for range offset 0000040 ((TimedOutException))
>
> Operation [38] retried 10 times - error on calling get_indexed_slices for range offset 0000038 ((TimedOutException))
>
> Operation [18] retried 10 times - error on calling get_indexed_slices for range offset 0000018 ((TimedOutException))
>
> Operation [31] retried 10 times - error on calling get_indexed_slices for range offset 0000031 ((TimedOutException))
>
> Operation [4] retried 10 times - error on calling get_indexed_slices for range offset 0000004 ((TimedOutException))
>
> Operation [22] retried 10 times - error on calling get_indexed_slices for range offset 0000022 ((TimedOutException))
>
> Operation [49] retried 10 times - error on calling get_indexed_slices for range offset 0000049 ((TimedOutException))
>
> Operation [41] retried 10 times - error on calling get_indexed_slices for range offset 0000041 ((TimedOutException))
>
> Operation [37] retried 10 times - error on calling get_indexed_slices for range offset 0000037 ((TimedOutException))
>
> Operation [13] retried 10 times - error on calling get_indexed_slices for range offset 0000013 ((TimedOutException))
>
> Operation [39] retried 10 times - error on calling get_indexed_slices for range offset 0000039 ((TimedOutException))
>
> Operation [21] retried 10 times - error on calling get_indexed_slices for range offset 0000021 ((TimedOutException))
>
> Operation [10] retried 10 times - error on calling get_indexed_slices for range offset 0000010 ((TimedOutException))
>
> Operation [17] retried 10 times - error on calling get_indexed_slices for range offset 0000017 ((TimedOutException))
>
> Operation [1] retried 10 times - error on calling get_indexed_slices for range offset 0000001 ((TimedOutException))
>
> Operation [42] retried 10 times - error on calling get_indexed_slices for range offset 0000042 ((TimedOutException))
>
> 0,0,0,NaN,106
> END
>
>
>
>
> On Dec 2, 2011, at 2:45 PM, Janne Jalkanen wrote:
>
>>
>> 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
>>> <pi...@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 <zl...@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
>>
>
>
> This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.
RE: [RELEASE] Apache Cassandra 1.0.5 released
Posted by mi...@thomsonreuters.com.
Hi Zhong Li,
When I used stress tool to test, I got:
Operation [15] retried 10 times - error inserting key 0015 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [37] retried 10 times - error inserting key 0037 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [17] retried 10 times - error inserting key 0017 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [40] retried 10 times - error inserting key 0040 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [28] retried 10 times - error inserting key 0028 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [2] retried 10 times - error inserting key 0002 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [13] retried 10 times - error inserting key 0013 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [29] retried 10 times - error inserting key 0029 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [30] retried 10 times - error inserting key 0030 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [23] retried 10 times - error inserting key 0023 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [21] retried 10 times - error inserting key 0021 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [42] retried 10 times - error inserting key 0042 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [0] retried 10 times - error inserting key 0000 ((InvalidRequestException): unconfigured columnfamily Standard1)
Operation [11] retried 10 times - error inserting key 0011 ((InvalidRequestException): unconfigured columnfamily Standard1)
0,0,0,NaN,0
END
Do I need to create the column family manually first, or it is created by the stress tool automatically? Why did I get the errors above?
Thanks,
Mike
-----Original Message-----
From: Zhong Li [mailto:zli@voxeo.com]
Sent: Friday, December 02, 2011 3:24 PM
To: user@cassandra.apache.org
Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
I just tested with stress tool, it is reproducible and timeout happens always.
./stress -d <mynode address> -e QUORUM -l 3 -o RANGE_SLICE
total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
0,0,0,NaN,10
0,0,0,NaN,20
0,0,0,NaN,30
0,0,0,NaN,40
0,0,0,NaN,50
0,0,0,NaN,60
0,0,0,NaN,70
0,0,0,NaN,80
0,0,0,NaN,91
0,0,0,NaN,101
Operation [2] retried 10 times - error on calling get_indexed_slices for range offset 0000002 ((TimedOutException))
Operation [46] retried 10 times - error on calling get_indexed_slices for range offset 0000046 ((TimedOutException))
Operation [47] retried 10 times - error on calling get_indexed_slices for range offset 0000047 ((TimedOutException))
Operation [24] retried 10 times - error on calling get_indexed_slices for range offset 0000024 ((TimedOutException))
Operation [45] retried 10 times - error on calling get_indexed_slices for range offset 0000045 ((TimedOutException))
Operation [48] retried 10 times - error on calling get_indexed_slices for range offset 0000048 ((TimedOutException))
Operation [5] retried 10 times - error on calling get_indexed_slices for range offset 0000005 ((TimedOutException))
Operation [28] retried 10 times - error on calling get_indexed_slices for range offset 0000028 ((TimedOutException))
Operation [0] retried 10 times - error on calling get_indexed_slices for range offset 0000000 ((TimedOutException))
Operation [23] retried 10 times - error on calling get_indexed_slices for range offset 0000023 ((TimedOutException))
Operation [32] retried 10 times - error on calling get_indexed_slices for range offset 0000032 ((TimedOutException))
Operation [36] retried 10 times - error on calling get_indexed_slices for range offset 0000036 ((TimedOutException))
Operation [16] retried 10 times - error on calling get_indexed_slices for range offset 0000016 ((TimedOutException))
Operation [6] retried 10 times - error on calling get_indexed_slices for range offset 0000006 ((TimedOutException))
Operation [9] retried 10 times - error on calling get_indexed_slices for range offset 0000009 ((TimedOutException))
Operation [11] retried 10 times - error on calling get_indexed_slices for range offset 0000011 ((TimedOutException))
Operation [25] retried 10 times - error on calling get_indexed_slices for range offset 0000025 ((TimedOutException))
Operation [26] retried 10 times - error on calling get_indexed_slices for range offset 0000026 ((TimedOutException))
Operation [43] retried 10 times - error on calling get_indexed_slices for range offset 0000043 ((TimedOutException))
Operation [27] retried 10 times - error on calling get_indexed_slices for range offset 0000027 ((TimedOutException))
Operation [33] retried 10 times - error on calling get_indexed_slices for range offset 0000033 ((TimedOutException))
Operation [44] retried 10 times - error on calling get_indexed_slices for range offset 0000044 ((TimedOutException))
Operation [19] retried 10 times - error on calling get_indexed_slices for range offset 0000019 ((TimedOutException))
Operation [35] retried 10 times - error on calling get_indexed_slices for range offset 0000035 ((TimedOutException))
Operation [34] retried 10 times - error on calling get_indexed_slices for range offset 0000034 ((TimedOutException))
Operation [30] retried 10 times - error on calling get_indexed_slices for range offset 0000030 ((TimedOutException))
Operation [14] retried 10 times - error on calling get_indexed_slices for range offset 0000014 ((TimedOutException))
Operation [7] retried 10 times - error on calling get_indexed_slices for range offset 0000007 ((TimedOutException))
Operation [20] retried 10 times - error on calling get_indexed_slices for range offset 0000020 ((TimedOutException))
Operation [3] retried 10 times - error on calling get_indexed_slices for range offset 0000003 ((TimedOutException))
Operation [8] retried 10 times - error on calling get_indexed_slices for range offset 0000008 ((TimedOutException))
Operation [15] retried 10 times - error on calling get_indexed_slices for range offset 0000015 ((TimedOutException))
Operation [29] retried 10 times - error on calling get_indexed_slices for range offset 0000029 ((TimedOutException))
Operation [12] retried 10 times - error on calling get_indexed_slices for range offset 0000012 ((TimedOutException))
Operation [40] retried 10 times - error on calling get_indexed_slices for range offset 0000040 ((TimedOutException))
Operation [38] retried 10 times - error on calling get_indexed_slices for range offset 0000038 ((TimedOutException))
Operation [18] retried 10 times - error on calling get_indexed_slices for range offset 0000018 ((TimedOutException))
Operation [31] retried 10 times - error on calling get_indexed_slices for range offset 0000031 ((TimedOutException))
Operation [4] retried 10 times - error on calling get_indexed_slices for range offset 0000004 ((TimedOutException))
Operation [22] retried 10 times - error on calling get_indexed_slices for range offset 0000022 ((TimedOutException))
Operation [49] retried 10 times - error on calling get_indexed_slices for range offset 0000049 ((TimedOutException))
Operation [41] retried 10 times - error on calling get_indexed_slices for range offset 0000041 ((TimedOutException))
Operation [37] retried 10 times - error on calling get_indexed_slices for range offset 0000037 ((TimedOutException))
Operation [13] retried 10 times - error on calling get_indexed_slices for range offset 0000013 ((TimedOutException))
Operation [39] retried 10 times - error on calling get_indexed_slices for range offset 0000039 ((TimedOutException))
Operation [21] retried 10 times - error on calling get_indexed_slices for range offset 0000021 ((TimedOutException))
Operation [10] retried 10 times - error on calling get_indexed_slices for range offset 0000010 ((TimedOutException))
Operation [17] retried 10 times - error on calling get_indexed_slices for range offset 0000017 ((TimedOutException))
Operation [1] retried 10 times - error on calling get_indexed_slices for range offset 0000001 ((TimedOutException))
Operation [42] retried 10 times - error on calling get_indexed_slices for range offset 0000042 ((TimedOutException))
0,0,0,NaN,106
END
On Dec 2, 2011, at 2:45 PM, Janne Jalkanen wrote:
>
> 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
>> <pi...@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 <zl...@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
>
This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.
Re: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Zhong Li <zl...@voxeo.com>.
I just tested with stress tool, it is reproducible and timeout happens always.
./stress -d <mynode address> -e QUORUM -l 3 -o RANGE_SLICE
total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
0,0,0,NaN,10
0,0,0,NaN,20
0,0,0,NaN,30
0,0,0,NaN,40
0,0,0,NaN,50
0,0,0,NaN,60
0,0,0,NaN,70
0,0,0,NaN,80
0,0,0,NaN,91
0,0,0,NaN,101
Operation [2] retried 10 times - error on calling get_indexed_slices for range offset 0000002 ((TimedOutException))
Operation [46] retried 10 times - error on calling get_indexed_slices for range offset 0000046 ((TimedOutException))
Operation [47] retried 10 times - error on calling get_indexed_slices for range offset 0000047 ((TimedOutException))
Operation [24] retried 10 times - error on calling get_indexed_slices for range offset 0000024 ((TimedOutException))
Operation [45] retried 10 times - error on calling get_indexed_slices for range offset 0000045 ((TimedOutException))
Operation [48] retried 10 times - error on calling get_indexed_slices for range offset 0000048 ((TimedOutException))
Operation [5] retried 10 times - error on calling get_indexed_slices for range offset 0000005 ((TimedOutException))
Operation [28] retried 10 times - error on calling get_indexed_slices for range offset 0000028 ((TimedOutException))
Operation [0] retried 10 times - error on calling get_indexed_slices for range offset 0000000 ((TimedOutException))
Operation [23] retried 10 times - error on calling get_indexed_slices for range offset 0000023 ((TimedOutException))
Operation [32] retried 10 times - error on calling get_indexed_slices for range offset 0000032 ((TimedOutException))
Operation [36] retried 10 times - error on calling get_indexed_slices for range offset 0000036 ((TimedOutException))
Operation [16] retried 10 times - error on calling get_indexed_slices for range offset 0000016 ((TimedOutException))
Operation [6] retried 10 times - error on calling get_indexed_slices for range offset 0000006 ((TimedOutException))
Operation [9] retried 10 times - error on calling get_indexed_slices for range offset 0000009 ((TimedOutException))
Operation [11] retried 10 times - error on calling get_indexed_slices for range offset 0000011 ((TimedOutException))
Operation [25] retried 10 times - error on calling get_indexed_slices for range offset 0000025 ((TimedOutException))
Operation [26] retried 10 times - error on calling get_indexed_slices for range offset 0000026 ((TimedOutException))
Operation [43] retried 10 times - error on calling get_indexed_slices for range offset 0000043 ((TimedOutException))
Operation [27] retried 10 times - error on calling get_indexed_slices for range offset 0000027 ((TimedOutException))
Operation [33] retried 10 times - error on calling get_indexed_slices for range offset 0000033 ((TimedOutException))
Operation [44] retried 10 times - error on calling get_indexed_slices for range offset 0000044 ((TimedOutException))
Operation [19] retried 10 times - error on calling get_indexed_slices for range offset 0000019 ((TimedOutException))
Operation [35] retried 10 times - error on calling get_indexed_slices for range offset 0000035 ((TimedOutException))
Operation [34] retried 10 times - error on calling get_indexed_slices for range offset 0000034 ((TimedOutException))
Operation [30] retried 10 times - error on calling get_indexed_slices for range offset 0000030 ((TimedOutException))
Operation [14] retried 10 times - error on calling get_indexed_slices for range offset 0000014 ((TimedOutException))
Operation [7] retried 10 times - error on calling get_indexed_slices for range offset 0000007 ((TimedOutException))
Operation [20] retried 10 times - error on calling get_indexed_slices for range offset 0000020 ((TimedOutException))
Operation [3] retried 10 times - error on calling get_indexed_slices for range offset 0000003 ((TimedOutException))
Operation [8] retried 10 times - error on calling get_indexed_slices for range offset 0000008 ((TimedOutException))
Operation [15] retried 10 times - error on calling get_indexed_slices for range offset 0000015 ((TimedOutException))
Operation [29] retried 10 times - error on calling get_indexed_slices for range offset 0000029 ((TimedOutException))
Operation [12] retried 10 times - error on calling get_indexed_slices for range offset 0000012 ((TimedOutException))
Operation [40] retried 10 times - error on calling get_indexed_slices for range offset 0000040 ((TimedOutException))
Operation [38] retried 10 times - error on calling get_indexed_slices for range offset 0000038 ((TimedOutException))
Operation [18] retried 10 times - error on calling get_indexed_slices for range offset 0000018 ((TimedOutException))
Operation [31] retried 10 times - error on calling get_indexed_slices for range offset 0000031 ((TimedOutException))
Operation [4] retried 10 times - error on calling get_indexed_slices for range offset 0000004 ((TimedOutException))
Operation [22] retried 10 times - error on calling get_indexed_slices for range offset 0000022 ((TimedOutException))
Operation [49] retried 10 times - error on calling get_indexed_slices for range offset 0000049 ((TimedOutException))
Operation [41] retried 10 times - error on calling get_indexed_slices for range offset 0000041 ((TimedOutException))
Operation [37] retried 10 times - error on calling get_indexed_slices for range offset 0000037 ((TimedOutException))
Operation [13] retried 10 times - error on calling get_indexed_slices for range offset 0000013 ((TimedOutException))
Operation [39] retried 10 times - error on calling get_indexed_slices for range offset 0000039 ((TimedOutException))
Operation [21] retried 10 times - error on calling get_indexed_slices for range offset 0000021 ((TimedOutException))
Operation [10] retried 10 times - error on calling get_indexed_slices for range offset 0000010 ((TimedOutException))
Operation [17] retried 10 times - error on calling get_indexed_slices for range offset 0000017 ((TimedOutException))
Operation [1] retried 10 times - error on calling get_indexed_slices for range offset 0000001 ((TimedOutException))
Operation [42] retried 10 times - error on calling get_indexed_slices for range offset 0000042 ((TimedOutException))
0,0,0,NaN,106
END
On Dec 2, 2011, at 2:45 PM, Janne Jalkanen wrote:
>
> 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
>> <pi...@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 <zl...@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
>
Re: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
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
> <pi...@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 <zl...@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
Re: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Jonathan Ellis <jb...@gmail.com>.
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
<pi...@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 <zl...@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
Re: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Pierre Belanger <pi...@xobni.com>.
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 <zl...@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) .
>
>
Re: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Zhong Li <zl...@voxeo.com>.
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) .
Re: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Evgeniy Ryabitskiy <ev...@wikimart.ru>.
+1
After upgrade to 1.0.5 also have Timeout exception on Secondary Index
search (get_indexed_slices API) .
RE: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Michael Vaknine <mi...@citypath.com>.
Hi,
After upgrading cluster to 1.0.5
I am having problems connecting to the cluster using hector
Any help will be aprichiated.
Thanks
Michael
me.prettyprint.hector.api.exceptions.HTimedOutException: TimedOutException()
at
me.prettyprint.cassandra.service.ExceptionsTranslatorImpl.translate(Exceptio
nsTranslatorImpl.java:42)
at
me.prettyprint.cassandra.service.KeyspaceServiceImpl$19.execute(KeyspaceServ
iceImpl.java:744)
at
me.prettyprint.cassandra.service.KeyspaceServiceImpl$19.execute(KeyspaceServ
iceImpl.java:726)
at
me.prettyprint.cassandra.service.Operation.executeAndSetResult(Operation.jav
a:101)
at
me.prettyprint.cassandra.connection.HConnectionManager.operateWithFailover(H
ConnectionManager.java:233)
at
me.prettyprint.cassandra.service.KeyspaceServiceImpl.operateWithFailover(Key
spaceServiceImpl.java:131)
at
me.prettyprint.cassandra.service.KeyspaceServiceImpl.getIndexedSlices(Keyspa
ceServiceImpl.java:748)
at
me.prettyprint.cassandra.model.IndexedSlicesQuery$1.doInKeyspace(IndexedSlic
esQuery.java:140)
at
me.prettyprint.cassandra.model.IndexedSlicesQuery$1.doInKeyspace(IndexedSlic
esQuery.java:131)
at
me.prettyprint.cassandra.model.KeyspaceOperationCallback.doInKeyspaceAndMeas
ure(KeyspaceOperationCallback.java:20)
at
me.prettyprint.cassandra.model.ExecutingKeyspace.doExecute(ExecutingKeyspace
.java:85)
at
me.prettyprint.cassandra.model.IndexedSlicesQuery.execute(IndexedSlicesQuery
.java:130)
at
com.lookin2.cassandra.access.CassandraImpl.executeQuery(CassandraImpl.java:2
20)
at
com.lookin2.cassandra.access.CassandraImpl.privateGet(CassandraImpl.java:327
)
at com.lookin2.cassandra.access.Cassandra.get(Cassandra.java:67)
at com.lookin2.cassandra.entities.BaseCass.getRows(BaseCass.java:150)
at com.lookin2.cassandra.entities.CassSet.populateOne(CassSet.java:148)
at com.lookin2.cassandra.entities.CassSet.populate(CassSet.java:117)
at
com.lookin2.cassandra.ontologies.CategoryAccess.getCategories(CategoryAccess
.java:20)
at
com.lookin2.cassandra.ontologies.CategoryOntologyCAO.loadAllNames(CategoryOn
tologyCAO.java:23)
at
com.lookin2.common.dawg.AbstractNamedItemTrie.init(AbstractNamedItemTrie.jav
a:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory
.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1536)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory
.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory
.initializeBean(AbstractAutowireCapableBeanFactory.java:1409)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory
.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory
.createBean(AbstractAutowireCapableBeanFactory.java:456)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(Ab
stractBeanFactory.java:291)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSi
ngleton(DefaultSingletonBeanRegistry.java:222)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(Abst
ractBeanFactory.java:288)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(Abstra
ctBeanFactory.java:190)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInst
antiateSingletons(DefaultListableBeanFactory.java:574)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFac
toryInitialization(AbstractApplicationContext.java:895)
at
org.springframework.context.support.AbstractApplicationContext.refresh(Abstr
actApplicationContext.java:425)
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(Co
ntextLoader.java:276)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(Cont
extLoader.java:197)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(Con
textLoaderListener.java:47)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:
3972)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4467)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
Caused by: TimedOutException()
at
org.apache.cassandra.thrift.Cassandra$get_indexed_slices_result.read(Cassand
ra.java:14073)
at
org.apache.cassandra.thrift.Cassandra$Client.recv_get_indexed_slices(Cassand
ra.java:810)
at
org.apache.cassandra.thrift.Cassandra$Client.get_indexed_slices(Cassandra.ja
va:782)
at
me.prettyprint.cassandra.service.KeyspaceServiceImpl$19.execute(KeyspaceServ
iceImpl.java:732)
... 53 more
-----Original Message-----
From: Sylvain Lebresne [mailto:sylvain@datastax.com]
Sent: Thursday, December 01, 2011 1:38 PM
To: user@cassandra.apache.org
Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
On Thu, Dec 1, 2011 at 11:58 AM, Michael Vaknine <mi...@citypath.com>
wrote:
> Unfortunately no.
>
> Second time I did the test:
>
> Restore 4 nodes to a new Cassandra cluster (0.7.8)
> Upgrade to 1.0.0
> Run nodetool scrub on each node after upgrade before upgrading next node.
> Upgrade to 1.0.3
> Upgrade to 1.0.5
> Run nodetool repair on all nodes.
> All process was successful.
>
> What does this error means and how is it affecting my cluster?
> Do you think it is safe to upgrade to 1.0.5 and disregard this error?
It's a race condition between the flush of a memtable and the flush of
it's secondary indexes. It's not specific to 1.0.5 at all (it's in 0.8,
probably
since 0.8.0), and it's very unlikely to happen (you're the first to report
it).
The error has not real effect (it cannot result in data corruption or
data loss).
I've created https://issues.apache.org/jira/browse/CASSANDRA-3547
to fix.
--
Sylvain
>
> Thanks
> Michael
>
>
> -----Original Message-----
> From: Jonathan Ellis [mailto:jbellis@gmail.com]
> Sent: Thursday, December 01, 2011 2:10 AM
> To: user@cassandra.apache.org
> Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
>
> I don't think so. That code hasn't changed in a long time. Is it
> reproducible?
>
> On Wed, Nov 30, 2011 at 2:46 PM, Michael Vaknine <mi...@citypath.com>
> wrote:
>> Hi,
>> Upgrade 1.0.3 to 1.0.5
>> I have this errors
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449
>> AbstractCassandraDaemon.java (line 133) Fatal exception in thread Thread
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449
> java.lang.AssertionError
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
>
org.apache.cassandra.db.ColumnFamilyStore.maybeSwitchMemtable(ColumnFamilySt
>> ore.java:671)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
>
org.apache.cassandra.db.ColumnFamilyStore.forceFlush(ColumnFamilyStore.java:
>> 745)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
>
org.apache.cassandra.db.ColumnFamilyStore.forceBlockingFlush(ColumnFamilySto
>> re.java:750)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
>
org.apache.cassandra.db.index.keys.KeysIndex.forceBlockingFlush(KeysIndex.ja
>> va:119)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
>
org.apache.cassandra.db.index.SecondaryIndexManager.flushIndexesBlocking(Sec
>> ondaryIndexManager.java:258)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
>
org.apache.cassandra.db.index.SecondaryIndexManager.maybeBuildSecondaryIndex
>> es(SecondaryIndexManager.java:123)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
>
org.apache.cassandra.streaming.StreamInSession.closeIfFinished(StreamInSessi
>> on.java:151)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
>
org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReade
>> r.java:103)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
>
org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.
>> java:184)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
>
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.jav
>> a:81)
>>
>> Is this another regression?
>>
>> Thanks
>> Michael
>>
>> -----Original Message-----
>> From: Brandon Williams [mailto:driftx@gmail.com]
>> Sent: Wednesday, November 30, 2011 9:43 PM
>> To: user@cassandra.apache.org
>> Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
>>
>> On Wed, Nov 30, 2011 at 1:29 PM, Michael Vaknine <mi...@citypath.com>
>> wrote:
>>> The files are not on the site
>>> The requested URL
>> /apache//cassandra/1.0.5/apache-cassandra-1.0.5-bin.tar.gz
>>> was not found on this server.
>>
>> It takes the mirrors some time to sync.
>>
>> -Brandon
>>
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>
Re: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Sylvain Lebresne <sy...@datastax.com>.
On Thu, Dec 1, 2011 at 11:58 AM, Michael Vaknine <mi...@citypath.com> wrote:
> Unfortunately no.
>
> Second time I did the test:
>
> Restore 4 nodes to a new Cassandra cluster (0.7.8)
> Upgrade to 1.0.0
> Run nodetool scrub on each node after upgrade before upgrading next node.
> Upgrade to 1.0.3
> Upgrade to 1.0.5
> Run nodetool repair on all nodes.
> All process was successful.
>
> What does this error means and how is it affecting my cluster?
> Do you think it is safe to upgrade to 1.0.5 and disregard this error?
It's a race condition between the flush of a memtable and the flush of
it's secondary indexes. It's not specific to 1.0.5 at all (it's in 0.8, probably
since 0.8.0), and it's very unlikely to happen (you're the first to report it).
The error has not real effect (it cannot result in data corruption or
data loss).
I've created https://issues.apache.org/jira/browse/CASSANDRA-3547
to fix.
--
Sylvain
>
> Thanks
> Michael
>
>
> -----Original Message-----
> From: Jonathan Ellis [mailto:jbellis@gmail.com]
> Sent: Thursday, December 01, 2011 2:10 AM
> To: user@cassandra.apache.org
> Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
>
> I don't think so. That code hasn't changed in a long time. Is it
> reproducible?
>
> On Wed, Nov 30, 2011 at 2:46 PM, Michael Vaknine <mi...@citypath.com>
> wrote:
>> Hi,
>> Upgrade 1.0.3 to 1.0.5
>> I have this errors
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449
>> AbstractCassandraDaemon.java (line 133) Fatal exception in thread Thread
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449
> java.lang.AssertionError
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
> org.apache.cassandra.db.ColumnFamilyStore.maybeSwitchMemtable(ColumnFamilySt
>> ore.java:671)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
> org.apache.cassandra.db.ColumnFamilyStore.forceFlush(ColumnFamilyStore.java:
>> 745)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
> org.apache.cassandra.db.ColumnFamilyStore.forceBlockingFlush(ColumnFamilySto
>> re.java:750)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
> org.apache.cassandra.db.index.keys.KeysIndex.forceBlockingFlush(KeysIndex.ja
>> va:119)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
> org.apache.cassandra.db.index.SecondaryIndexManager.flushIndexesBlocking(Sec
>> ondaryIndexManager.java:258)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
> org.apache.cassandra.db.index.SecondaryIndexManager.maybeBuildSecondaryIndex
>> es(SecondaryIndexManager.java:123)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
> org.apache.cassandra.streaming.StreamInSession.closeIfFinished(StreamInSessi
>> on.java:151)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
> org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReade
>> r.java:103)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
> org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.
>> java:184)
>> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>>
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.jav
>> a:81)
>>
>> Is this another regression?
>>
>> Thanks
>> Michael
>>
>> -----Original Message-----
>> From: Brandon Williams [mailto:driftx@gmail.com]
>> Sent: Wednesday, November 30, 2011 9:43 PM
>> To: user@cassandra.apache.org
>> Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
>>
>> On Wed, Nov 30, 2011 at 1:29 PM, Michael Vaknine <mi...@citypath.com>
>> wrote:
>>> The files are not on the site
>>> The requested URL
>> /apache//cassandra/1.0.5/apache-cassandra-1.0.5-bin.tar.gz
>>> was not found on this server.
>>
>> It takes the mirrors some time to sync.
>>
>> -Brandon
>>
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>
RE: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Michael Vaknine <mi...@citypath.com>.
Unfortunately no.
Second time I did the test:
Restore 4 nodes to a new Cassandra cluster (0.7.8)
Upgrade to 1.0.0
Run nodetool scrub on each node after upgrade before upgrading next node.
Upgrade to 1.0.3
Upgrade to 1.0.5
Run nodetool repair on all nodes.
All process was successful.
What does this error means and how is it affecting my cluster?
Do you think it is safe to upgrade to 1.0.5 and disregard this error?
Thanks
Michael
-----Original Message-----
From: Jonathan Ellis [mailto:jbellis@gmail.com]
Sent: Thursday, December 01, 2011 2:10 AM
To: user@cassandra.apache.org
Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
I don't think so. That code hasn't changed in a long time. Is it
reproducible?
On Wed, Nov 30, 2011 at 2:46 PM, Michael Vaknine <mi...@citypath.com>
wrote:
> Hi,
> Upgrade 1.0.3 to 1.0.5
> I have this errors
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449
> AbstractCassandraDaemon.java (line 133) Fatal exception in thread Thread
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449
java.lang.AssertionError
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>
org.apache.cassandra.db.ColumnFamilyStore.maybeSwitchMemtable(ColumnFamilySt
> ore.java:671)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>
org.apache.cassandra.db.ColumnFamilyStore.forceFlush(ColumnFamilyStore.java:
> 745)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>
org.apache.cassandra.db.ColumnFamilyStore.forceBlockingFlush(ColumnFamilySto
> re.java:750)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>
org.apache.cassandra.db.index.keys.KeysIndex.forceBlockingFlush(KeysIndex.ja
> va:119)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>
org.apache.cassandra.db.index.SecondaryIndexManager.flushIndexesBlocking(Sec
> ondaryIndexManager.java:258)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>
org.apache.cassandra.db.index.SecondaryIndexManager.maybeBuildSecondaryIndex
> es(SecondaryIndexManager.java:123)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>
org.apache.cassandra.streaming.StreamInSession.closeIfFinished(StreamInSessi
> on.java:151)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>
org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReade
> r.java:103)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>
org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.
> java:184)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
>
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.jav
> a:81)
>
> Is this another regression?
>
> Thanks
> Michael
>
> -----Original Message-----
> From: Brandon Williams [mailto:driftx@gmail.com]
> Sent: Wednesday, November 30, 2011 9:43 PM
> To: user@cassandra.apache.org
> Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
>
> On Wed, Nov 30, 2011 at 1:29 PM, Michael Vaknine <mi...@citypath.com>
> wrote:
>> The files are not on the site
>> The requested URL
> /apache//cassandra/1.0.5/apache-cassandra-1.0.5-bin.tar.gz
>> was not found on this server.
>
> It takes the mirrors some time to sync.
>
> -Brandon
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
Re: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Jonathan Ellis <jb...@gmail.com>.
I don't think so. That code hasn't changed in a long time. Is it reproducible?
On Wed, Nov 30, 2011 at 2:46 PM, Michael Vaknine <mi...@citypath.com> wrote:
> Hi,
> Upgrade 1.0.3 to 1.0.5
> I have this errors
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449
> AbstractCassandraDaemon.java (line 133) Fatal exception in thread Thread
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 java.lang.AssertionError
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
> org.apache.cassandra.db.ColumnFamilyStore.maybeSwitchMemtable(ColumnFamilySt
> ore.java:671)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
> org.apache.cassandra.db.ColumnFamilyStore.forceFlush(ColumnFamilyStore.java:
> 745)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
> org.apache.cassandra.db.ColumnFamilyStore.forceBlockingFlush(ColumnFamilySto
> re.java:750)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
> org.apache.cassandra.db.index.keys.KeysIndex.forceBlockingFlush(KeysIndex.ja
> va:119)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
> org.apache.cassandra.db.index.SecondaryIndexManager.flushIndexesBlocking(Sec
> ondaryIndexManager.java:258)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
> org.apache.cassandra.db.index.SecondaryIndexManager.maybeBuildSecondaryIndex
> es(SecondaryIndexManager.java:123)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
> org.apache.cassandra.streaming.StreamInSession.closeIfFinished(StreamInSessi
> on.java:151)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
> org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReade
> r.java:103)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
> org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.
> java:184)
> TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.jav
> a:81)
>
> Is this another regression?
>
> Thanks
> Michael
>
> -----Original Message-----
> From: Brandon Williams [mailto:driftx@gmail.com]
> Sent: Wednesday, November 30, 2011 9:43 PM
> To: user@cassandra.apache.org
> Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
>
> On Wed, Nov 30, 2011 at 1:29 PM, Michael Vaknine <mi...@citypath.com>
> wrote:
>> The files are not on the site
>> The requested URL
> /apache//cassandra/1.0.5/apache-cassandra-1.0.5-bin.tar.gz
>> was not found on this server.
>
> It takes the mirrors some time to sync.
>
> -Brandon
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
RE: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Michael Vaknine <mi...@citypath.com>.
Hi,
Upgrade 1.0.3 to 1.0.5
I have this errors
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449
AbstractCassandraDaemon.java (line 133) Fatal exception in thread Thread
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 java.lang.AssertionError
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
org.apache.cassandra.db.ColumnFamilyStore.maybeSwitchMemtable(ColumnFamilySt
ore.java:671)
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
org.apache.cassandra.db.ColumnFamilyStore.forceFlush(ColumnFamilyStore.java:
745)
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
org.apache.cassandra.db.ColumnFamilyStore.forceBlockingFlush(ColumnFamilySto
re.java:750)
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
org.apache.cassandra.db.index.keys.KeysIndex.forceBlockingFlush(KeysIndex.ja
va:119)
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
org.apache.cassandra.db.index.SecondaryIndexManager.flushIndexesBlocking(Sec
ondaryIndexManager.java:258)
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
org.apache.cassandra.db.index.SecondaryIndexManager.maybeBuildSecondaryIndex
es(SecondaryIndexManager.java:123)
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
org.apache.cassandra.streaming.StreamInSession.closeIfFinished(StreamInSessi
on.java:151)
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReade
r.java:103)
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.
java:184)
TST-Cass2 ERROR [Thread-58] 2011-11-30 20:40:17,449 at
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.jav
a:81)
Is this another regression?
Thanks
Michael
-----Original Message-----
From: Brandon Williams [mailto:driftx@gmail.com]
Sent: Wednesday, November 30, 2011 9:43 PM
To: user@cassandra.apache.org
Subject: Re: [RELEASE] Apache Cassandra 1.0.5 released
On Wed, Nov 30, 2011 at 1:29 PM, Michael Vaknine <mi...@citypath.com>
wrote:
> The files are not on the site
> The requested URL
/apache//cassandra/1.0.5/apache-cassandra-1.0.5-bin.tar.gz
> was not found on this server.
It takes the mirrors some time to sync.
-Brandon
Re: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Brandon Williams <dr...@gmail.com>.
On Wed, Nov 30, 2011 at 1:29 PM, Michael Vaknine <mi...@citypath.com> wrote:
> The files are not on the site
> The requested URL /apache//cassandra/1.0.5/apache-cassandra-1.0.5-bin.tar.gz
> was not found on this server.
It takes the mirrors some time to sync.
-Brandon
RE: [RELEASE] Apache Cassandra 1.0.5 released
Posted by Michael Vaknine <mi...@citypath.com>.
The files are not on the site
The requested URL /apache//cassandra/1.0.5/apache-cassandra-1.0.5-bin.tar.gz
was not found on this server.
Thanks,
Michael
-----Original Message-----
From: Sylvain Lebresne [mailto:sylvain@datastax.com]
Sent: Wednesday, November 30, 2011 9:11 PM
To: user@cassandra.apache.org
Subject: [RELEASE] Apache Cassandra 1.0.5 released
As indicated in a preceding mail (http://goo.gl/R1r1V), the release of 1.0.4
unfortunately shipped with two important regressions. The Cassandra team is
pleased to announce the release of Apache Cassandra version 1.0.5 that comes
to fix those two issues[1], but is identical to 1.0.4 otherwise.
Cassandra 1.0.5 can be de downloaded in the usual places, i.e:
http://cassandra.apache.org/download/
We sincerely apologize for any inconvenience caused by 1.0.4. As always,
please pay attention to the release notes[2] and Let us know[3] if you were
to
encounter any problem.
Have fun!
[1]: http://goo.gl/Fod0B (CHANGES.txt)
[2]: http://goo.gl/gtUvs (NEWS.txt)
[3]: https://issues.apache.org/jira/browse/CASSANDRA