[jira] [Commented] (CASSANDRA-9213) Compaction errors observed during heavy write load: BAD RELEASE
[
https://issues.apache.org/jira/browse/CASSANDRA-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574081#comment-14574081
]
Marcus Eriksson commented on CASSANDRA-9213:
[~rocco.varela] sorry for the delay on this, were you dropping/recreating
tables during your testing? were you able to reproduce with debugrefcount on?
Compaction errors observed during heavy write load: BAD RELEASE
---
Key: CASSANDRA-9213
URL: https://issues.apache.org/jira/browse/CASSANDRA-9213
Project: Cassandra
Issue Type: Bug
Environment: Cassandra 2.1.4.374
Ubuntu 14.04.2
java version 1.7.0_45
10-node cluster, RF = 3
Reporter: Rocco Varela
Assignee: Marcus Eriksson
Fix For: 2.1.x
Attachments: COMPACTION-ERR.log
During heavy write load testing we're seeing occasional compaction errors
with the following error message:
{code}
ERROR [CompactionExecutor:40] 2015-04-16 17:01:16,936 Ref.java:170 - BAD
RELEASE: attempted to release a reference
(org.apache.cassandra.utils.concurrent.Ref$State@31d969bd) that has
already been released
...
ERROR [CompactionExecutor:40] 2015-04-16 17:01:22,190
CassandraDaemon.java:223 - Exception in thread
Thread[CompactionExecutor:40,1,main]
java.lang.AssertionError: null
at
org.apache.cassandra.io.sstable.SSTableReader.markObsolete(SSTableReader.java:1699)
~[cassandra-all-2.1.4.374.jar:2.1.4.374]
at
org.apache.cassandra.db.DataTracker.unmarkCompacting(DataTracker.java:240)
~[cassandra-all-2.1.4.374.jar:2.1.4.374]
at
org.apache.cassandra.io.sstable.SSTableRewriter.replaceWithFinishedReaders(SSTableRewriter.java:495)
~[cassandra-all-2.1.4.374.jar:2.1.4.374]
at
...
{code}
I have turned on debugrefcount in bin/cassandra:launch_service() and I will
repost another stack trace when it happens again.
{code}
cassandra_parms=$cassandra_parms -Dcassandra.debugrefcount=true
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9213) Compaction errors observed during heavy write load: BAD RELEASE
[
https://issues.apache.org/jira/browse/CASSANDRA-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14574709#comment-14574709
]
Rocco Varela commented on CASSANDRA-9213:
-
Yes I was dropping and recreating tables, followed by periods of heavy write
load. Unfortunately this issue is not reliably reproducible and I was not able
to recreate this error with debugrefcount turned on.
Compaction errors observed during heavy write load: BAD RELEASE
---
Key: CASSANDRA-9213
URL: https://issues.apache.org/jira/browse/CASSANDRA-9213
Project: Cassandra
Issue Type: Bug
Environment: Cassandra 2.1.4.374
Ubuntu 14.04.2
java version 1.7.0_45
10-node cluster, RF = 3
Reporter: Rocco Varela
Assignee: Marcus Eriksson
Fix For: 2.1.x
Attachments: COMPACTION-ERR.log
During heavy write load testing we're seeing occasional compaction errors
with the following error message:
{code}
ERROR [CompactionExecutor:40] 2015-04-16 17:01:16,936 Ref.java:170 - BAD
RELEASE: attempted to release a reference
(org.apache.cassandra.utils.concurrent.Ref$State@31d969bd) that has
already been released
...
ERROR [CompactionExecutor:40] 2015-04-16 17:01:22,190
CassandraDaemon.java:223 - Exception in thread
Thread[CompactionExecutor:40,1,main]
java.lang.AssertionError: null
at
org.apache.cassandra.io.sstable.SSTableReader.markObsolete(SSTableReader.java:1699)
~[cassandra-all-2.1.4.374.jar:2.1.4.374]
at
org.apache.cassandra.db.DataTracker.unmarkCompacting(DataTracker.java:240)
~[cassandra-all-2.1.4.374.jar:2.1.4.374]
at
org.apache.cassandra.io.sstable.SSTableRewriter.replaceWithFinishedReaders(SSTableRewriter.java:495)
~[cassandra-all-2.1.4.374.jar:2.1.4.374]
at
...
{code}
I have turned on debugrefcount in bin/cassandra:launch_service() and I will
repost another stack trace when it happens again.
{code}
cassandra_parms=$cassandra_parms -Dcassandra.debugrefcount=true
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9213) Compaction errors observed during heavy write load: BAD RELEASE
[
https://issues.apache.org/jira/browse/CASSANDRA-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14503079#comment-14503079
]
Philip Thompson commented on CASSANDRA-9213:
/cc [~krummas]
Compaction errors observed during heavy write load: BAD RELEASE
---
Key: CASSANDRA-9213
URL: https://issues.apache.org/jira/browse/CASSANDRA-9213
Project: Cassandra
Issue Type: Bug
Environment: Cassandra 2.1.4.374
Ubuntu 14.04.2
java version 1.7.0_45
10-node cluster, RF = 3
Reporter: Rocco Varela
Fix For: 2.1.5
Attachments: COMPACTION-ERR.log
During heavy write load testing we're seeing occasional compaction errors
with the following error message:
{code}
ERROR [CompactionExecutor:40] 2015-04-16 17:01:16,936 Ref.java:170 - BAD
RELEASE: attempted to release a reference
(org.apache.cassandra.utils.concurrent.Ref$State@31d969bd) that has
already been released
...
ERROR [CompactionExecutor:40] 2015-04-16 17:01:22,190
CassandraDaemon.java:223 - Exception in thread
Thread[CompactionExecutor:40,1,main]
java.lang.AssertionError: null
at
org.apache.cassandra.io.sstable.SSTableReader.markObsolete(SSTableReader.java:1699)
~[cassandra-all-2.1.4.374.jar:2.1.4.374]
at
org.apache.cassandra.db.DataTracker.unmarkCompacting(DataTracker.java:240)
~[cassandra-all-2.1.4.374.jar:2.1.4.374]
at
org.apache.cassandra.io.sstable.SSTableRewriter.replaceWithFinishedReaders(SSTableRewriter.java:495)
~[cassandra-all-2.1.4.374.jar:2.1.4.374]
at
...
{code}
I have turned on debugrefcount in bin/cassandra:launch_service() and I will
repost another stack trace when it happens again.
{code}
cassandra_parms=$cassandra_parms -Dcassandra.debugrefcount=true
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
