You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2015/12/17 16:49:46 UTC
[jira] [Commented] (CASSANDRA-10895) The return of CASSANDRA-8718?
[ https://issues.apache.org/jira/browse/CASSANDRA-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062216#comment-15062216 ]
Sylvain Lebresne commented on CASSANDRA-10895:
----------------------------------------------
It does seem that we've closed CASSANDRA-8718 without really finding out what was going wrong. Assigning [~JoshuaMcKenzie] just because he was assigned previously, but feel free to re-assign if you don't have any cycles on this.
> The return of CASSANDRA-8718?
> -----------------------------
>
> Key: CASSANDRA-10895
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10895
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Environment: Cassandra 2.1.9 running on:
> ubuntu@ip-10-250-1-225:~$ uname -a
> Linux ip-10-250-1-225 3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> ubuntu@ip-10-250-1-225:~$ java -version
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> ubuntu@ip-10-250-1-225:~$
> Reporter: Pete Ehlke
> Assignee: Joshua McKenzie
> Attachments: hs_err_pid317.log
>
>
> Repeatable every time I run 'nodetool repair -inc -par' on this host:
> 2015-12-17_14:32:30.78574 INFO 14:32:30 Writing Memtable-sstable_activity@907762948(95.060KiB serialized bytes, 17729 ops, 0%/0% of on/off-heap limi
> t)
> 2015-12-17_14:32:30.80120 INFO 14:32:30 Completed flushing /data/cassandra/data/system/sstable_activity-5a1ff267ace03f128563cfae6103c65e/system-ssta
> ble_activity-tmp-ka-2126-Data.db (75.676KiB) for commitlog position ReplayPosition(segmentId=1449246749652, position=3079886)
> 2015-12-17_14:32:32.67513 #
> 2015-12-17_14:32:32.67516 # A fatal error has been detected by the Java Runtime Environment:
> 2015-12-17_14:32:32.67517 #
> 2015-12-17_14:32:32.67518 # SIGSEGV (0xb) at pc=0x00007f477699117a, pid=317, tid=139942572054272
> 2015-12-17_14:32:32.67525 #
> 2015-12-17_14:32:32.67526 # JRE version: Java(TM) SE Runtime Environment (8.0_60-b27) (build 1.8.0_60-b27)
> 2015-12-17_14:32:32.67527 # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode linux-amd64 compressed oops)
> 2015-12-17_14:32:32.67528 # Problematic frame:
> 2015-12-17_14:32:32.67529 # J 21341 C2 org.apache.cassandra.io.sstable.IndexSummary.binarySearch(Lorg/apache/cassandra/db/RowPosition;)I (88 bytes) @ 0x00007f477699117a [0x00007f4776991020+0x15a]
> 2015-12-17_14:32:32.67532 #
> 2015-12-17_14:32:32.67533 # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> 2015-12-17_14:32:32.67535 #
> 2015-12-17_14:32:32.67587 # An error report file with more information is saved as:
> 2015-12-17_14:32:32.67587 # /tmp/hs_err_pid317.log
> 2015-12-17_14:32:32.69831 #
> 2015-12-17_14:32:32.69832 # If you would like to submit a bug report, please visit:
> 2015-12-17_14:32:32.69832 # http://bugreport.java.com/bugreport/crash.jsp
> 2015-12-17_14:32:32.69832 #
> This looks exactly like CASSANDRA-8718, but that was marked as fixed in 2.0.13
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)