[
https://issues.apache.org/jira/browse/CASSANDRA-15531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891240#comment-17891240
]
Michael Semb Wever commented on CASSANDRA-15531:
------------------------------------------------
It was agreed in (the ML thread behind) CASSANDRA-19021 to change the default
from auto to mmap_index_only.
5.0+ provides more information in cassandra.yaml, and there's now also
commitlog_disk_access_mode
More concerns about instabilities caused from using mmap, and unclear benefits
of using it in combination with compression, was also discussed in slack here:
https://the-asf.slack.com/archives/CK23JSY2K/p1729275981044059
> Improve docs on disk_access_mode, specifically post CASSANDRA-8464
> ------------------------------------------------------------------
>
> Key: CASSANDRA-15531
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15531
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation
> Reporter: Erick Ramirez (deprecated)
> Assignee: Erick Ramirez
> Priority: Normal
> Labels: documentation
>
> h2. Background
> [~tsteinmaurer] brought up [on
> Slack|https://the-asf.slack.com/archives/CJZLTM05A/p1580298424288700] that
> they've been hit by the `oom-killer` as a result of SSTables being mmaped.
> h2. Action
> Based on feedback from Thomas Steinmaurer, Jean Carlo & Sam Kearon, I am
> going to push the info I've written in this KB article to the official docs –
> [Increased memory use on nodes after upgrading to DSE 5.0 or DSE
> 5.1|https://support.datastax.com/s/article/Increased-memory-use-on-nodes-after-upgrading-to-DSE-50-or-DSE-51].
> I will revise it specifically for affected OSS versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
