[
https://issues.apache.org/jira/browse/CASSANDRA-17161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752325#comment-17752325
]
Stefan Miklosovic commented on CASSANDRA-17161:
-----------------------------------------------
j17
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2862/workflows/cfe54ce7-78df-483f-98e7-f6d5a38f0868
j11
https://app.circleci.com/pipelines/github/instaclustr/cassandra/2862/workflows/76ab92a6-3495-4889-bb04-4efd0b2ea439
PR https://github.com/apache/cassandra/pull/2533
CCM PR https://github.com/riptano/ccm/pull/754
dtest PR https://github.com/apache/cassandra-dtest/pull/230
[~brandon.williams] I will need your assistance with CCM patch. I made it
backward compatible and I changed dtests accordingly.
> Remove commitlog_sync_batch_window_in_ms
> ----------------------------------------
>
> Key: CASSANDRA-17161
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17161
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Ekaterina Dimitrova
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> commitlog_sync_batch_window_in_ms is deprecated in 4.0 and has to be removed
> in 5.0
> This will require also some work around the in-jvm upgrade tests.
> Currently they do not work if we remove a parameter in a later version.
> Side note: They also don't work if we change the type of the parameter in
> Config class in a newer Cassandra version. If you plan to set it in the tests
> themselves, it won't work. If you change the type but your don't set the
> parameter, no issue so there might be some workaround solution instead of
> working on the dtest framework itself.... TBD
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
