cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6749) -Dcassandra.boot_without_jna=true does not actually disable JNA
Date Fri, 21 Feb 2014 04:34:19 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907946#comment-13907946
] 

Ryan McGuire commented on CASSANDRA-6749:
-----------------------------------------

OK, looks like if ccm is going to have an option to disable it we need to actually delete
it from the lib dir (or prevent it from getting into the CP.) Thanks for the clarification.


> -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)

Mime
View raw message