Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 23 Apr 2013 13:59:17 +0000 (UTC)
From: "Jeremy Hanna (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12644093.1366715862897.208003.1366725557534@arcas>
In-Reply-To: <JIRA.12644093.1366715862897@arcas>
References: <JIRA.12644093.1366715862897@arcas>
Subject: [jira] [Updated] (CASSANDRA-5508) Expose whether jna is enabled and
 memory is locked via JMX
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremy Hanna updated CASSANDRA-5508:
------------------------------------

    Summary: Expose whether jna is enabled and memory is locked via JMX  (was: Expose whether jna is enabled via JMX)
    
> Expose whether jna is enabled and memory is locked via JMX
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-5508
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5508
>             Project: Cassandra
>          Issue Type: Wish
>            Reporter: Jeremy Hanna
>            Priority: Trivial
>
> This may not be possible, but it would be very useful.  Currently the only definitive way to determine whether JNA is enabled and that it's able to lock the memory it needs is to look at the startup log.
> It would be great if there was a way to store whether it is enabled so that jmx (or nodetool) could easily tell if JNA was enabled and whether it was able to lock the memory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira