[
https://issues.apache.org/jira/browse/CASSANDRA-8993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377985#comment-14377985
]
Benedict commented on CASSANDRA-8993:
-------------------------------------
[~Hachmann]: Yes, that's the expectation - I'm as certain as I can be that this
will prevent the underlying bug causing any problems. We would love for you to
corroborate this in the wild, though, by deploying the patch if you can.
> 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.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)
