cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-5737) CassandraDaemon - recent unsafe memory access operation in compiled Java code
Date Tue, 09 Jul 2013 14:51:51 GMT


Jonathan Ellis resolved CASSANDRA-5737.

    Resolution: Invalid

FTR, here's CommitLogSegment lines 124..126 in 1.2.6:

            buffer = logFileAccessor.getChannel().map(FileChannel.MapMode.READ_WRITE, 0, DatabaseDescriptor.getCommitLogSegmentSize());

This is definitely a bug at either the JVM or Linux level, so I'm going to close this as Invalid
at the Cassandra level, but please do update us with what you find.  (Ubuntu has a bit of
a track record of shipping unreliable kernels, FWIW.  Try Debian stable?)
> CassandraDaemon - recent unsafe memory access operation in compiled Java code
> -----------------------------------------------------------------------------
>                 Key: CASSANDRA-5737
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.6
>         Environment: Amazon EC2, XLarge instance.
> Ubuntu 12.04.2 LTS
> Raid 0 disks, with ext4 
>            Reporter: Glyn Davies
> I'm using 1.2.6 on Ubuntu AWS m1.xlarge instances with the Datastax Community package
and have tried using Java versions jdk1.7.0_25  jre1.6.0_45
> Also testing with and without libjna-java (ie the JNA jar)
> However, something has triggered a bug in the CassandraDaemon:
> ERROR [COMMIT-LOG-ALLOCATOR] 2013-07-05 15:00:51,663 (line 192)
Exception in thread Thread[COMMIT-LOG-ALLOCATOR,5,main]
> java.lang.InternalError: a fault occurred in a recent unsafe memory access operation
in compiled Java code
>         at org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(
>         at org.apache.cassandra.db.commitlog.CommitLogSegment.freshSegment(
>         at org.apache.cassandra.db.commitlog.CommitLogAllocator.createFreshSegment(
>         at org.apache.cassandra.db.commitlog.CommitLogAllocator.access$500(
>         at org.apache.cassandra.db.commitlog.CommitLogAllocator$1.runMayThrow(
>         at
>         at Source)
> This brought two nodes down out of a three node cluster – using QUORUM write with 3
> Restarting the node replays this error, so I have the system in a 'stable' unstable state
– which is probably a good place for trouble shooting.
> Presumably something a client wrote triggered this situation, and the other third node
was to be the final replication point – and is thus still up.
> Subsequently discovered that only a reboot will allow that node to come back up.
> Java Bug raised with Oracle after finding a Java dump text indicating a SIGBUS.
> At this point, I'm thinking that there is potentially a Linux kernel bug being triggered?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message