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-8709) Convert SequentialWriter from using RandomAccessFile to nio channel
Date Thu, 19 Feb 2015 19:40:11 GMT

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

Benedict commented on CASSANDRA-8709:
-------------------------------------

I think a case can be made to move SegmentedFile to this instead of RAR as well. This would
permit us to avoid creating a separate file handle for either each instance _or_ each reader.
Since we're only competing against other buffered readers here (not touching mmapping), I
think the improvement could be well worthwhile, and likely have no downside. There may be
some follow on benefits as well, by being able to refactor our writing a little to eliminate
both TMP and TMPLINK files.

> Convert SequentialWriter from using RandomAccessFile to nio channel
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-8709
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8709
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Joshua McKenzie
>            Assignee: Joshua McKenzie
>              Labels: Windows
>             Fix For: 3.0
>
>
> For non-mmap'ed I/O on Windows, using nio channels will give us substantially more flexibility
w/regards to renaming and moving files around while writing them.  This change in conjunction
with CASSANDRA-4050 should allow us to remove the Windows bypass code in SSTableRewriter for
non-memory-mapped I/O.
> In general, migrating from instances of RandomAccessFile to nio channels will help make
Windows and linux behavior more consistent.



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

Mime
View raw message