[
https://issues.apache.org/jira/browse/CASSANDRA-8993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-8993:
-----------------------------------
Attachment: 8993-2.1-v2.txt
> EffectiveIndexInterval calculation is incorrect
> -----------------------------------------------
>
> Key: CASSANDRA-8993
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8993
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Priority: Blocker
> Fix For: 2.1.4
>
> Attachments: 8993-2.1-v2.txt, 8993-2.1.txt, 8993.txt
>
>
> I'm not familiar enough with the calculation itself to understand why this is
> happening, but see discussion on CASSANDRA-8851 for the background. I've
> introduced a test case to look for this during downsampling, but it seems to
> pass just fine, so it may be an artefact of upgrading.
> The problem was, unfortunately, not manifesting directly because it would
> simply result in a failed lookup. This was only exposed when early opening
> used firstKeyBeyond, which does not use the effective interval, and provided
> the result to getPosition().
> I propose a simple fix that ensures a bug here cannot break correctness.
> Perhaps [~thobbs] can follow up with an investigation as to how it actually
> went wrong?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
