cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Stump (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8160) CF level option to call posix_fadvise for sstables on creation and startup
Date Thu, 26 Feb 2015 19:45:05 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339018#comment-14339018
] 

Matt Stump commented on CASSANDRA-8160:
---------------------------------------

After learning how the new implementation of the in memory stuff works with DSE I don't think
it would be a good idea to move forward with this ticket. Using mlock seems like a much better
way to tackle this problem.

> CF level option to call posix_fadvise for sstables on creation and startup
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8160
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8160
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Matt Stump
>            Assignee: Branimir Lambov
>            Priority: Minor
>             Fix For: 2.1.4
>
>         Attachments: trunk-8160.txt
>
>
> We should have a CF level configuration with will result in posix_fadvise being called
for sstables for that CF. It should be called on node startup and for new sstables. This should
be configurable per CF to allow for some CFs to be prioritized above others. Not sure if we
should use POSIX_FADV_SEQUENTIAL or POSIX_FADV_WILLNEED. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message