You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Doug Rohrer (Jira)" <ji...@apache.org> on 2024/06/27 17:20:00 UTC

[jira] [Assigned] (CASSANDRA-19730) In-JVM dtest JMX support should support nodetool usage

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

Doug Rohrer reassigned CASSANDRA-19730:
---------------------------------------

    Assignee: Doug Rohrer

> In-JVM dtest JMX support should support nodetool usage
> ------------------------------------------------------
>
>                 Key: CASSANDRA-19730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19730
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Doug Rohrer
>            Assignee: Doug Rohrer
>            Priority: Normal
>
> As we continue to push the boundaries of what the in-jvm dtest framework can do, we’ve found an edge-case where nodetool can’t create a NodeProbe instance because the JVM memory and Runtime mbeans aren’t exposed via the IsolatedJmx class. Registering these when starting up an IsolatedJmx instance allows NodeProbe to be properly instantiated and the nodetool command-line tool to work correctly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org