Details
-
Improvement
-
Status: Triage Needed
-
Normal
-
Resolution: Unresolved
-
None
-
None
-
None
-
All
-
None
Description
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.
Attachments
Issue Links
- relates to
-
CASSANDRA-18572 Instance.nodetoolResult should connect to JMX if there is such feature enabled in its config
- Patch Available