cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (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 15:52:05 GMT

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

Benedict commented on CASSANDRA-8160:
-------------------------------------

bq. Perform reads on startup in the compation thread pool? 

Seems reasonable.

bq. Do we block until it's complete?

I'm agnostic on this, so long as it's documented what the behaviour is. It could even be optional,
but given we're catering for a narrow crowd, it's probably not worth polluting with too many
knobs.

> 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