[
https://issues.apache.org/jira/browse/CASSANDRA-15767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094773#comment-17094773
]
David Capwell commented on CASSANDRA-15767:
-------------------------------------------
When cassandra starts up it runs a set of checks to see how the environment is.
Some checks will cause cassandra to fail starting up, others will log warnings
saying cassandra may be impacted; the main checks can be found
[here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StartupChecks.java#L85].
If you change jemalloc to allow .2 then the jemalloc check won't log the
warning, but the other ones still will since they are independent checks.
For the ENOMEM issue, I don't think we document this well (though glad to
accept improvements on this!), same for "nofile limit adequate? ".
> /usr/bin/cassandra looking for wrong libjemalloc.so file
> --------------------------------------------------------
>
> Key: CASSANDRA-15767
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15767
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Scripts
> Reporter: Brian Bellrose
> Priority: Normal
>
> In /usr/sbin/cassandra
> Linux)
> if [ -z $CASSANDRA_LIBJEMALLOC ] ; then
> which ldconfig > /dev/null 2>&1
> if [ $? = 0 ] ; then
> # e.g. for CentOS
> dirs="/lib64 /lib /usr/lib64 /usr/lib `ldconfig -v 2>/dev/null | grep -v
> '^\s' | sed 's/^\([^:]*\):.*$/\1/'`"
> else
> # e.g. for Debian, OpenSUSE
> dirs="/lib64 /lib /usr/lib64 /usr/lib `cat /etc/ld.so.conf
> /etc/ld.so.conf.d/*.conf | grep '^/'`"
> fi
> dirs=`echo $dirs | tr " " ":"`
> CASSANDRA_LIBJEMALLOC=$(find_library '.*/libjemalloc\.so\(\.1\)*' $dirs)
>
> However...
> # find /usr/lib64 -name "*jemalloc*"
> /usr/lib64/libjemalloc.so.2
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
