[
https://issues.apache.org/jira/browse/CASSANDRA-17389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493938#comment-17493938
]
Muhammad commented on CASSANDRA-17389:
--------------------------------------
Yeah, I can try that out meanwhile. But I don't see any changes in the
*sun.misc.Unsafe* usage with the latest 3.x version, so I think that will not
fix the issue.
> JVM Crashing with SIGSEGV for Cassandra 3.11.3
> ----------------------------------------------
>
> Key: CASSANDRA-17389
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17389
> Project: Cassandra
> Issue Type: Bug
> Reporter: Muhammad
> Priority: Normal
> Attachments: hs_err.txt
>
>
> I am running a Cassandra 3.11.3 cluster with latest Corretto-8 and seeing JVM
> crashes with SIGSEGV signal at random intervals across various Cassandra
> nodes. This crash seems to happen more frequently while I am doing rolling
> restarts on the cluster.
> I am attaching the JVM error report for the crashes that are observed here in
> this case. [^hs_err.txt]
> Looking at the error report, it appears that the problematic frame is
> {*}binarySearch{*}, which ultimately calls
> [this|https://github.com/apache/cassandra/blob/cassandra-3.11.3/src/java/org/apache/cassandra/utils/memory/MemoryUtil.java#L175].
> As per my knowledge, it is not recommended to use the sun.misc.Unsafe
> outside the JDK. Could you please advice here.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
