[
https://issues.apache.org/jira/browse/CASSANDRA-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790909#comment-14790909
]
T Jake Luciani commented on CASSANDRA-10357:
--------------------------------------------
{code}
List<Long> boundaries = new ArrayList<>(this.boundaries);
{code}
The scope of boundaries var is probably why this was overlooked initially. Can
you make this more obvious?
We should add a note in NEWS.txt for users upgrading. I guess anyone who has
compression turned off potentially needs to run upgradesstables :/
Any way to add a test for this easily?
Can you link the dtest and testall runs?
> mmap file boundary selection is broken for some large files
> ------------------------------------------------------------
>
> Key: CASSANDRA-10357
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10357
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Fix For: 2.1.10
>
>
> If an early open interval occurs to close to an mmap boundary, the boundary
> can be lost. Patch available
> [here|https://github.com/belliottsmith/cassandra/tree/mmap-boundaries].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
