cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10628) get JEMAlloc debug output out of nodetool output
Date Wed, 04 Nov 2015 22:34:27 GMT


Robert Stupp commented on CASSANDRA-10628:

Works on both OSX and Linux (latest Debian).
Thanks, committed as 0ff13d2a6847f7ecba1ac9a26b66714d9e58b60d to 2.2, 3.0, trunk

> get JEMAlloc debug output out of nodetool output
> ------------------------------------------------
>                 Key: CASSANDRA-10628
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>            Assignee: Robert Stupp
>             Fix For: 2.2.4, 3.0.0
> 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}}:
> You can reproduce the excessive output with
> {code}
> ccm create test-nodetool-output -v git:cassandra-3.0 -n 1 ; ccm start --wait-for-binary-proto
; ccm node1 nodetool ring
> {code}
> 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 [~snazy] for now; feel free to reassign

This message was sent by Atlassian JIRA

View raw message