cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3930) CommitLogSegment uses RandomAccessFile which doesnt have fadvice
Date Fri, 17 Feb 2012 17:35:59 GMT

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

Jonathan Ellis commented on CASSANDRA-3930:
-------------------------------------------

CASSANDRA-3578 has some patches that mean commitlog i/o may not be strictly sequential.
                
> CommitLogSegment uses RandomAccessFile which doesnt have fadvice
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-3930
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3930
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.0.7
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.1.1, 1.2
>
>
> Wondering if we even need MMap file in this case as it is always sequential.
> If yes, we need it we might want to replace 
> logFileAccessor = new RandomAccessFile(logFile, "rw");
> to
> logFileAccessor = SequentialWriter.open(logFile, true);
> in CommitLogSegment

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message