[
https://issues.apache.org/jira/browse/CASSANDRA-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-18220:
--------------------------------------
Change Category: Quality Assurance
Complexity: Low Hanging Fruit
Fix Version/s: NA
Status: Open (was: Triage Needed)
> In CI when cassandra crashes and produces a jvm error file, we do not archive
> this and just show in logs that the JVM crashed
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18220
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18220
> Project: Cassandra
> Issue Type: Improvement
> Components: CI
> Reporter: David Capwell
> Priority: Normal
> Fix For: NA
>
>
> When the jvm produces an error file we should make sure to back it up in CI.
> This can be as simple as adding the following env
> {code}
> JAVA_TOOL_OPTIONS: '-XX:ErrorFile=DIR_WE_BACKUP/hs_err_pid_%p.log'
> {code}
--
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
