[
https://issues.apache.org/jira/browse/CASSANDRA-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900885#comment-14900885
]
Benedict commented on CASSANDRA-10357:
--------------------------------------
I've pushed a new version, with tests included, and the boundary logic
rewritten, as I encountered another bug while fixing it and decided it was time
to make the boundary logic more consistent across all users (this bug was
related to the fact we do not serialize the length into the file, and if we
haven't updated the length as a "potential boundary" we may not serialize the
boundary just before the length into the file - in which case when we
deserialize the bounds the last segment may be larger than {{MAX_SEGMENT_SIZE}}
even though it didn't need to be).
> 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)
