[
https://issues.apache.org/jira/browse/CASSANDRA-10511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977217#comment-14977217
]
Ariel Weisberg commented on CASSANDRA-10511:
--------------------------------------------
Is this true for 3.0 after [~Stefania]'s work? I remember reviewing that and
looking at the code we don't use the readable bounds anymore?
We use it at runtime for early opening just to denote the end of the file, but
that is it.
For 2.1 and 2.2 yeah it looks like short of backporting Stefania's work we
should populate the boundaries.
> Index summary downsampling prevents mmap access of large files after restart
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-10511
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10511
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Benedict
> Fix For: 2.1.x, 2.2.x, 3.1
>
>
> {{SSTableReader.cloneWithNewSummarySampleLevel}} constructs a
> {{SegmentedFile.Builder}} but never populates it with any boundaries. For
> files larger than 2Gb, this will result in their being accessed via buffered
> io after a restart.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
