On Wed, Sep 12, 2012 at 9:38 AM, Janne Jalkanen
wrote:
> OK, so what's the worst case here? Data loss? Bad performance?
Low performance is for sure a side effect. I can't comment on data
loss (and I'm curious about as well) because it depends on how data
off of an out-of-order sstable was being i
On 12 Sep 2012, at 00:50, Omid Aladini wrote:
> On Tue, Sep 11, 2012 at 8:33 PM, Janne Jalkanen
> wrote:
>>
>> Does this mean that LCS on 1.0.x should be considered unsafe to
>> use? I'm using them for semi-wide frequently-updated CounterColumns
>> and they're performing much better on LCS than
Based on the steps outlined here
https://issues.apache.org/jira/browse/CASSANDRA-4644?focusedCommentId=13453156&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13453156it
seems that LCS was not used until after 1.1.4 and they were able to do
a
full repair cleanup compa
On Tue, Sep 11, 2012 at 8:33 PM, Janne Jalkanen
wrote:
>
>> A bug in Cassandra 1.1.2 and earlier could cause out-of-order sstables
>> and inter-level overlaps in CFs with Leveled Compaction. Your sstables
>> generated with 1.1.3 and later should not have this issue [1] [2].
>
> Does this mean that
> A bug in Cassandra 1.1.2 and earlier could cause out-of-order sstables
> and inter-level overlaps in CFs with Leveled Compaction. Your sstables
> generated with 1.1.3 and later should not have this issue [1] [2].
Does this mean that LCS on 1.0.x should be considered unsafe to use? I'm using
th
> Could you, as Aaron suggested, open a ticket?
>
Done: https://issues.apache.org/jira/browse/CASSANDRA-4644
Could you, as Aaron suggested, open a ticket?
-- Omid
On Tue, Sep 11, 2012 at 2:35 PM, Rudolf van der Leeden
wrote:
>> Which version of Cassandra has your data been created initially with?
>> A bug in Cassandra 1.1.2 and earlier could cause out-of-order sstables
>> and inter-level overlaps in CF
>
> Which version of Cassandra has your data been created initially with?
> A bug in Cassandra 1.1.2 and earlier could cause out-of-order sstables
> and inter-level overlaps in CFs with Leveled Compaction. Your sstables
> generated with 1.1.3 and later should not have this issue [1] [2].
> In case
Which version of Cassandra has your data been created initially with?
A bug in Cassandra 1.1.2 and earlier could cause out-of-order sstables
and inter-level overlaps in CFs with Leveled Compaction. Your sstables
generated with 1.1.3 and later should not have this issue [1] [2].
In case you have o
> My question: Can these assertions be ignored? Or do I need to worry about it?
That looks like a problem.
Can you raise a ticket on https://issues.apache.org/jira/browse/CASSANDRA ?
May be good to include information on:
* how long you've been using Levelled Compaction.
* Is this all CF's or jus
Hi,
I'm getting 5 identical assertions while running 'nodetool cleanup' on a
Cassandra 1.1.4 node with Load=104G and 80m keys.
>From system.log :
ERROR [CompactionExecutor:576] 2012-09-10 11:25:50,265
AbstractCassandraDaemon.java (line 134) Exception in thread
Thread[CompactionExecutor:576,1,mai
11 matches
Mail list logo
