[CASSANDRA-19820] Fix tests extending FuzzTestBase when running test-compression profile

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-rc2, 5.0.1, 5.1
• Component/s: Local/Commit Log, Test/unit
• Bug Category: Code
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: Unit Test
• Platform: All
• Since Version: 5.0-rc1

Source Control Link

https://github.com/apache/cassandra/commit/aca11d4fc3e5938510dc48c071b49e6d22f54497

Test and Documentation Plan

CI

• Assignee: Stefan Miklosovic
• Reporter: Stefan Miklosovic

Authors

Stefan Miklosovic

Reviewers

Michael Semb Wever

• Created: 08/Aug/24 18:27
• Updated: 09/Aug/24 12:32
• Resolved: 09/Aug/24 12:32

Description

FuzzTestBase extends CQLTester.InMemory which uses jimfs filesystem instead of the real one. This does not play well with direct mode of commitlog_disk_access_mode. We fixed this in CASSANDRA-19779 by always setting it to mmap. This does not work when we run tests in test-compression profile because then it expects "standard" mode and if fails on asserts.

The solution to fix test-compression profile is to set commitlog_disk_access_mode to mmap only in case it was indeed resolved to direct and not every time.

Issue Links

• is caused by: CASSANDRA-19779 direct IO support is always evaluated to false upon the very first start of a node
• links to: GitHub Pull Request #3464