[
https://issues.apache.org/jira/browse/CASSANDRA-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683387#comment-17683387
]
Stefan Miklosovic edited comment on CASSANDRA-17773 at 2/2/23 1:17 PM:
-----------------------------------------------------------------------
also, I am not completely sure why that is happening, but when I execute
"bin/nodetool status", it gives me this output:
{code}
$ ./bin/nodetool status
CompilerOracle: dontinline
org/apache/cassandra/db/Columns$Serializer.deserializeLargeSubset
(Lorg/apache/cassandra/io/util/DataInputPlus;Lorg/apache/cassandra/db/Columns;I)Lorg/apache/cassandra/db/Columns;
CompilerOracle: dontinline
org/apache/cassandra/db/Columns$Serializer.serializeLargeSubset
(Ljava/util/Collection;ILorg/apache/cassandra/db/Columns;ILorg/apache/cassandra/io/util/DataOutputPlus;)V
CompilerOracle: dontinline
org/apache/cassandra/db/Columns$Serializer.serializeLargeSubsetSize
(Ljava/util/Collection;ILorg/apache/cassandra/db/Columns;I)I
..... omitted for brevity
Datacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID
Rack
UN 127.0.0.1 238.76 KiB 16 100.0%
2f747977-340c-48f1-a641-4e0b933e9661 rack1
{code}
where is that log before the nodetool invocation coming from?
EDIT:
It is coming from here (1) as we are sourcing cassandra-env.sh in
cassandra-conf.sh. I guess we need to find some way how to not put it among
JVM_OPTS when it is run as a script to not pollute the output unnecessarily.
(1) https://github.com/apache/cassandra/blob/trunk/conf/cassandra-env.sh#L191
EDIT 2:
The reason it is not happening in trunk is that there is currently this in
nodetool script:
{code}
# Run cassandra-env.sh to pick up JMX_PORT
if [ -f "$CASSANDRA_CONF/cassandra-env.sh" ]; then
JVM_OPTS_SAVE=$JVM_OPTS
MAX_HEAP_SIZE_SAVE=$MAX_HEAP_SIZE
. "$CASSANDRA_CONF/cassandra-env.sh"
MAX_HEAP_SIZE=$MAX_HEAP_SIZE_SAVE
JVM_OPTS="$JVM_OPTS_SAVE"
fi
{code}
So we are saving options to JVM_OPTS_SAVE, then run cassandra-env.sh which sets
its own JVM_OPTS and then we return to JVM_OPTS_SAVE. I think this is done
somehow differently in the current version hence the log is written with these
compiler hints.
was (Author: smiklosovic):
also, I am not completely sure why that is happening, but when I execute
"bin/nodetool status", it gives me this output:
{code}
$ ./bin/nodetool status
CompilerOracle: dontinline
org/apache/cassandra/db/Columns$Serializer.deserializeLargeSubset
(Lorg/apache/cassandra/io/util/DataInputPlus;Lorg/apache/cassandra/db/Columns;I)Lorg/apache/cassandra/db/Columns;
CompilerOracle: dontinline
org/apache/cassandra/db/Columns$Serializer.serializeLargeSubset
(Ljava/util/Collection;ILorg/apache/cassandra/db/Columns;ILorg/apache/cassandra/io/util/DataOutputPlus;)V
CompilerOracle: dontinline
org/apache/cassandra/db/Columns$Serializer.serializeLargeSubsetSize
(Ljava/util/Collection;ILorg/apache/cassandra/db/Columns;I)I
..... omitted for brevity
Datacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID
Rack
UN 127.0.0.1 238.76 KiB 16 100.0%
2f747977-340c-48f1-a641-4e0b933e9661 rack1
{code}
where is that log before the nodetool invocation coming from?
EDIT:
It is coming from here (1) as we are sourcing cassandra-env.sh in
cassandra-conf.sh. I guess we need to find some way how to not put it among
JVM_OPTS when it is run as a script to not pollute the output unnecessarily.
(1) https://github.com/apache/cassandra/blob/trunk/conf/cassandra-env.sh#L191
> Incorrect cassandra.logdir on Debian systems
> --------------------------------------------
>
> Key: CASSANDRA-17773
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17773
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Reporter: Eric Evans
> Assignee: Claude Warren
> Priority: Normal
> Labels: lhf
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> The Debian packaging patches bin/cassandra to use /var/log/cassandra for
> logs, it does so conditionally however, only if CASSANDRA_LOG_DIR is unset.
> This occurs _after_ cassandra-env.sh is sourced though, which also sets
> CASSANDRA_LOG_DIR if unset (to $CASSANDRA_HOME/logs). The result is that
> -Dcassandra.lodir is set to /usr/share/cassandra/logs on Debian systems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
