Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-10581

Update cassandra.yaml comments to reflect memory_allocator deprecation, remove in 3.0

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 2.2.4, 3.0.0
    • None
    • None
    • Normal

    Description

      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. Robert Stupp, 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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            snazy Robert Stupp Assign to me
            mambocab Jim Witschey
            Robert Stupp
            Jim Witschey
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment