[jira] [Updated] (CASSANDRA-17223) Node can be left in a bad state after invalid memory access exception

["Paulo Motta (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-17223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paulo Motta updated CASSANDRA-17223:
------------------------------------
    Labels: lhf  (was: )

> Node can be left in a bad state after invalid memory access exception
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-17223
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17223
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local/Other
>            Reporter: Paulo Motta
>            Priority: Normal
>              Labels: lhf
>
> There were a few reports of errors containing the following exception: {noformat}java.lang.InternalError: a fault occurred in a recent unsafe memory access operation in compiled Java {noformat} (CASSANDRA-8642, CASSANDRA-5737, CASSANDRA-11201, CASSANDRA-13091), normally closed as invalid due to the difficulty in reproducing it.
> This exception can be thrown in a [variety of scenarios|https://stackoverflow.com/a/45536678] generally involving a kernel fault during unsafe memory access.
> I've seen an occurence of this issue where the node went into a bad state after a memory access error.
> I believe this exception should be treated analogous to `OutOfMemoryException` (CASSANDRA-13006 ) and cause the process to crash if/when encountered, perhaps guarded by a flag.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org