[
https://issues.apache.org/jira/browse/CASSANDRA-17725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573958#comment-17573958
]
Ekaterina Dimitrova commented on CASSANDRA-17725:
-------------------------------------------------
CI results:
4.1 -
[test_parent_repair_session_cleanup|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1830/workflows/0ca3086d-6651-4f06-acab-2cd2ea208d93/jobs/14139/tests#failed-test-0]
failed for port being potentially busy to be used by Jolokia, I think this is
environmental seen with different tests before
trunk -
[transient_replication_test.TestTransientReplicationRepairStreamEntireSSTable|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1829/workflows/b123b955-9fbb-413e-a2a5-8f654dabee1f/jobs/14193/tests#failed-test-0]
failed for port being potentially busy to be used by Jolokia, same as the
previous one
Also, I reran those two tests locally and they pass successfully.
Starting commit soon.
> Add a flag for throughput in MiB/s for nodetool setstreamthroughput,
> getstreamthroughput, setinterdcstreamthroughput and
> getinterdcstreamthroughput
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17725
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17725
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.1-beta, 4.x
>
>
> As we agreed not to add new JMX methods for the new config on the mailing
> list, we need at least new flags for setstreamthroughput and
> interdcstreamthroughput for the two 4.0 parameters to be set/get also in MiB,
> not only in megabits.
> Thus we will have the option either to use the old version for those 2, or to
> be able to set/get in MiB all 4 streaming parameters. As of 4.1 supported
> units for DataRateSpec are MiB/s, B/s, KiB/s, megabit is only for legacy from
> 4.0 - backward compatibility.
> To be sure we satisfy the requirements around the latest discussions about
> backward compatibility in tools, I will use this ticket also to make a final
> pass on the unit changes done, to ensure the probe output is not affected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
