[
https://issues.apache.org/jira/browse/CASSANDRA-8729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314409#comment-14314409
]
T Jake Luciani commented on CASSANDRA-8729:
-------------------------------------------
I found a workaround by setting the segment size > the total commit log space
size. this drops the segment after each segment is full and it resolved this
issue.
> Commitlog causes read before write when overwriting
> ---------------------------------------------------
>
> Key: CASSANDRA-8729
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8729
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Ariel Weisberg
> Labels: commitlog
>
> The memory mapped commit log implementation writes directly to the page
> cache. If a page is not in the cache the kernel will read it in even though
> we are going to overwrite.
> The way to avoid this is to write to private memory, and then pad the write
> with 0s at the end so it is page (4k) aligned before writing to a file.
> The commit log would benefit from being refactored into something that looks
> more like a pipeline with incoming requests receiving private memory to write
> in, completed buffers being submitted to a parallelized compression/checksum
> step, followed by submission to another thread for writing to a file that
> preserves the order.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
