[CASSANDRA-16664] Log JVM Arguments at in-JVM Test Class Initialization

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0
• Component/s: Test/dtest/java
• Labels: ghc-lhf lhf
• Change Category: Operability
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/9a0dd603b18ab5034df27443a4bbc10111edcd8b

Test and Documentation Plan

Testing was done with CircleCI 

• Assignee: Natnael Adere
• Reporter: Caleb Rackliffe

Authors

Natnael Adere

Reviewers

Caleb Rackliffe, David Capwell

• Created: 10/May/21 22:29
• Updated: 12/Sep/23 13:02
• Resolved: 02/Nov/22 17:19

Description

Normal C* startup flows through CassandraDaemon.setup(), which calls logSystemInfo(), logging JVM arguments and a number of other useful bits of information. The in-JVM dtest startup does not flow through CassandraDaemon.setup(), and therefore does not. It would be useful for troubleshooting purposes if TestBaseImpl logged the JVM arguments before moving into executing tests.