cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brosius (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5508) Expose whether jna is enabled and memory is locked via JMX
Date Sun, 02 Jun 2013 17:50:20 GMT

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

Dave Brosius commented on CASSANDRA-5508:
-----------------------------------------

ok, sorry saw the fix version 2.0 and thought that's what you wanted.

welp, when git allows pushes again, i'll fix it.
                
> 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
>            Assignee: Dave Brosius
>            Priority: Trivial
>             Fix For: 2.0
>
>         Attachments: 5508.txt
>
>
> 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

Mime
View raw message