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

get JEMAlloc debug output out of nodetool output

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 2.2.4, 3.0.0
    • Component/s: None
    • Labels:
      None
    • Severity:
      Normal

      Description

      This is a followup ticket for CASSANDRA-10581. The consensus on the Cassandra TE is that the debug output for loading JEMAlloc is helpful (or at least harmless when starting C*, but not when starting nodetool, which, it turns out, sources cassandra-env:

      https://github.com/apache/cassandra/blob/trunk/bin/nodetool#L53

      You can reproduce the excessive output with

      ccm create test-nodetool-output -v git:cassandra-3.0 -n 1 ; ccm start --wait-for-binary-proto ; ccm node1 nodetool ring
      

      The simplest solution would probably be to redirect the output of the sourcing to /dev/null/. I don't know if that's the right thing to do; it may be better to move the LD_PRELOAD-setting logic to bin/cassandra. I'm not sure what the reasoning would be for putting something in one place or another, so I leave it to the dev team to decide on the best solution.

      Assigning Robert Stupp for now; feel free to reassign

        Attachments

          Activity

            People

            • Assignee:
              snazy Robert Stupp
              Reporter:
              mambocab Jim Witschey
              Authors:
              Robert Stupp
              Reviewers:
              Ariel Weisberg
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: