cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (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:30:20 GMT

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

Brandon Williams commented on CASSANDRA-6749:
---------------------------------------------

Perhaps the naming of the flag is slight misleading in favor of brevity, but it's not meant
to disable JNA, simply allow booting without it.  If JNA succeeds it isn't even checked and
there has never been a way to have JNA in the CP but disable it in cassandra.

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