You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2023/06/07 11:24:00 UTC
[jira] [Updated] (CASSANDRA-18572) Instance.nodetoolResult should connect to JMX if there is such feature enabled in its config
[ https://issues.apache.org/jira/browse/CASSANDRA-18572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Miklosovic updated CASSANDRA-18572:
------------------------------------------
Change Category: Quality Assurance
Complexity: Normal
Component/s: Test/dtest/java
Fix Version/s: 5.x
Assignee: Stefan Miklosovic
Status: Open (was: Triage Needed)
Instance.nodetoolResult is not using JMX internally but it throws UnsupportedOperationException in InternalNodeProbe.
This makes calls to instance.nodetoolResult("info"), for example, impossible, because these commands are using JMX / calling methods which are throwing exception and it makes the testing painful.
There is no reason to support this if Instance has JMX feature as it was added recently.
> Instance.nodetoolResult should connect to JMX if there is such feature enabled in its config
> --------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18572
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18572
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/java
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
>
--
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