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

Ekaterina Dimitrova edited comment on CASSANDRA-17668 at 9/26/22 3:44 PM:
--------------------------------------------------------------------------

Committed to trunk:

To [https://github.com/apache/cassandra.git]

   7adfdc85cf..e5c9cf4cbe  trunk -> trunk

The only issues seen were known:

test_move_backwards_and_cleanup - CASSANDRA-16061

test_multiple_repair - CASSANDRA-17005

Also, for the record - I didn't run in the multiplexer the unit tests because 
they cannot be more deterministic than that. Saved some resources here. 

Thank you for your work [~lmtrombone]!


was (Author: e.dimitrova):
Committed to trunk:

To https://github.com/apache/cassandra.git

   7adfdc85cf..e5c9cf4cbe  trunk -> trunk

The only issues seen were known:

test_move_backwards_and_cleanup - CASSANDRA-16061

test_multiple_repair - CASSANDRA-17005

Also, for the record - I didn't run in the multiplexer the unit tests because 
they cannot be more deterministic than that. Saved some resources here. 

> Fix leak of non-standard Java types in our Exceptions as clients using JMX 
> are unable to handle them
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17668
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17668
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/Observability, Observability/JMX
>            Reporter: Ekaterina Dimitrova
>            Assignee: Leonard Ma
>            Priority: Normal
>             Fix For: 4.2
>
>         Attachments: Screen Shot 2022-09-13 at 11.27.30 PM.png
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> This is a continuation of CASSANDRA-17638 where we fixed leaks introduced 
> during development of 4.1 to ensure no regressions.
> This ticket is to fix a few leakages which are there since previous major 
> versions, not 4.1 regressions. 
> {_}setRepairSessionMaxTreeDepth{_}(exists since 3.0) and 
> _setRepairSessionSpaceInMegabytes(since 4.0)_
>  in the DatabaseDescriptor. 
> checkValidForByteConversion and _validateMaxConcurrentAutoUpgradeTasksConf 
> (both since 4.0)_
>  are used in both setters and on startup. They shouldn't throw 
> ConfigurationException in the setters. 
> There might be more but those are at least a few obvious I found in the 
> DatabaseDescriptor.
> CC [~dcapwell] 



--
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

Reply via email to