cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10581) Update cassandra.yaml comments to reflect memory_allocator deprecation, remove in 3.0
Date Fri, 23 Oct 2015 16:46:27 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko updated CASSANDRA-10581:
------------------------------------------
    Reviewer: Jim Witschey

> 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.x, 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?



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

Mime
View raw message