Details
-
Bug
-
Status: Triage Needed
-
Normal
-
Resolution: Unresolved
-
None
-
All
-
None
Description
There were a few reports of errors containing the following exception:
java.lang.InternalError: a fault occurred in a recent unsafe memory access operation in compiled Java
(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 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.
Attachments
Issue Links
- is related to
-
CASSANDRA-5737 CassandraDaemon - recent unsafe memory access operation in compiled Java code
- Resolved
-
CASSANDRA-8642 Cassandra crashed after stress test of write
- Resolved
-
CASSANDRA-11201 Compaction memory fault in 3.0.3
- Resolved
-
CASSANDRA-13091 SASIIndexTest.testTableRebuild throws unsafe memory access exception
- Resolved