You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ryan McGuire (JIRA)" <ji...@apache.org> on 2014/02/21 04:13:24 UTC
[jira] [Created] (CASSANDRA-6749) -Dcassandra.boot_without_jna=true
does not actually disable JNA
Ryan McGuire created CASSANDRA-6749:
---------------------------------------
Summary: -Dcassandra.boot_without_jna=true does not actually disable JNA
Key: CASSANDRA-6749
URL: https://issues.apache.org/jira/browse/CASSANDRA-6749
Project: Cassandra
Issue Type: Bug
Reporter: Ryan McGuire
Priority: Minor
The JVM argument '-Dcassandra.boot_without_jna=true' appropriately allows Cassandra to start if the jna jar file *is missing* from the lib directory. However, in the case that the jar *does* exist, this flag does not actually disable JNA.
I am basing this assertion on the fact that even when I use this flag I see my entire heap space is preallocated (mlockall.) and by restarting after removing the jna jar file, the heapspace is not preallocated.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)