cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13366) Possible AssertionError in UnfilteredRowIteratorWithLowerBound
Date Mon, 27 Mar 2017 15:35:41 GMT


Philip Thompson commented on CASSANDRA-13366:

If the test is going to take more than a few days after the ticket, could we get a separate
jira ticket, maybe a subtask for that? I would hate to see it be forgotten and then no test

> Possible AssertionError in UnfilteredRowIteratorWithLowerBound
> --------------------------------------------------------------
>                 Key: CASSANDRA-13366
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 3.11.0
> In the code introduced by CASSANDRA-8180, we build a lower bound for a partition (sometimes)
based on the min clustering values of the stats file. We can't do that if the sstable has
and range tombston marker and the code does check that this is the case, but unfortunately
the check is done using the stats {{minLocalDeletionTime}} but that value isn't populated
properly in pre-3.0. This means that if you upgrade from 2.1/2.2 to 3.4+, you may end up getting
an exception like
> {noformat}
> WARN  [ReadStage-2] 2017-03-20 13:29:39,165
- Uncaught exception on thread Thread[ReadStage-2,5,main]: {}
> java.lang.AssertionError: Lower bound [INCL_START_BOUND(Foo, -9223372036854775808, -9223372036854775808)
]is bigger than first returned value [Marker INCL_START_BOUND(Foo)@1490013810540999] for sstable
>     at org.apache.cassandra.db.rows.UnfilteredRowIteratorWithLowerBound.computeNext(
> {noformat}
> and this until the sstable is upgraded.

This message was sent by Atlassian JIRA

View raw message