[
https://issues.apache.org/jira/browse/CASSANDRA-10581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985435#comment-14985435
]
Sylvain Lebresne commented on CASSANDRA-10581:
----------------------------------------------
I'm all for visibility, but it would a lot better to have in the log file imo.
Maybe we can set some custom environment variable based on our detection of
JEMalloc, or pass some system option to the binary, so that we can do such
logging.
> Update cassandra.yaml comments to reflect memory_allocator deprecation,
> remove in 3.0
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10581
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10581
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jim Witschey
> Assignee: Robert Stupp
> Fix For: 2.2.4, 3.0.0
>
>
> Looks like in 2.2+ changing the {{memory_allocator}} field in cassandra.yaml
> has no effect:
> https://github.com/apache/cassandra/commit/0d2ec11c7e0abfb84d872289af6d3ac386cf381f#diff-b66584c9ce7b64019b5db5a531deeda1R207
> The instructions in comments on how to use jemalloc haven't been updated to
> reflect this change. [~snazy], is that an accurate assessment?
> [~iamaleksey] How do we want to handle the deprecation more generally? Warn
> on 2.2, remove in 3.0?
> EDIT: I described this in a way that isn't very clear to those unfamiliar
> with Robert's change. To be clear: You can still use JEMAlloc with Cassandra.
> The {{memory_allocator}} option was deprecated in favor of automatically
> detecting if JEMAlloc is installed, and, if so, using it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
