cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wright (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6948) Native & ReplicateOnWriteStage AssertionError: Callback already exists
Date Fri, 28 Mar 2014 16:18:16 GMT


Keith Wright commented on CASSANDRA-6948:

Cassandra.log contains logging output from 010 node that just showed the issue including thread
dump prior to restart.  Let me know if you need me to upload it again.

These were completely distinct clusters.  FWIW, I have also noticed that applying DDLs on
nodes doesn't appear to always get applied to all nodes.  I am planning on filing a ticket
for that as soon as I can reproduce in a testing environment.  Workaround is to just apply
the same DDL on the nodes where the change did not appear.  I've often found 008 (the same
node showing the assertion error to the highest degree) to be the DDL culprit.

> Native & ReplicateOnWriteStage AssertionError: Callback already exists
> ----------------------------------------------------------------------
>                 Key: CASSANDRA-6948
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Keith Wright
>            Assignee: Benedict
>         Attachments: 6948.debug.txt, Screen Shot 2014-03-28 at 11.27.56 AM.png, Screen
Shot 2014-03-28 at 11.29.24 AM.png, cassandra.log.gz, cassandra.yaml, logs.old.tar.gz, logs.tar.gz,
system.log.1.gz, system.log.gz
> We are using the datastax driver and have seen the following exceptions appear periodically
in our cluster in "groups".  The client will gradually start sending less write requests to
the nodes where this occurs the most often.  This may be related to CASSANDRA-6476.  Exception
from logs:
> ERROR [Native-Transport-Requests:7636] 2014-03-28 13:32:10,638 (line
222) Unexpected exception during request
> java.lang.AssertionError: Callback already exists for id -1665979622! (CallbackInfo(target=/,
callback=org.apache.cassandra.service.WriteResponseHandler@5d36d8ea, serializer=org.apache.cassandra.db.WriteResponse$WriteResponseSerializer@6ed37f0b))
> 	at
> 	at
> 	at org.apache.cassandra.service.StorageProxy.mutateCounter(
> 	at org.apache.cassandra.service.StorageProxy.mutate(
> 	at org.apache.cassandra.service.StorageProxy.mutateWithTriggers(
> 	at org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(
> 	at org.apache.cassandra.cql3.statements.ModificationStatement.execute(
> 	at org.apache.cassandra.cql3.QueryProcessor.processStatement(
> 	at org.apache.cassandra.cql3.QueryProcessor.processPrepared(
> 	at org.apache.cassandra.transport.messages.ExecuteMessage.execute(
> 	at org.apache.cassandra.transport.Message$Dispatcher.messageReceived(
> 	at org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.doRun(
> 	at
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at
> ERROR [ReplicateOnWriteStage:102766] 2014-03-28 13:32:10,638 (line
196) Exception in thread Thread[ReplicateOnWriteStage:102766,5,main]
> java.lang.AssertionError: Callback already exists for id -1665979620! (CallbackInfo(target=/,
callback=org.apache.cassandra.service.WriteResponseHandler@3bdb1a75, serializer=org.apache.cassandra.db.WriteResponse$WriteResponseSerializer@6ed37f0b))
> 	at
> 	at
> 	at org.apache.cassandra.service.StorageProxy.sendToHintedEndpoints(
> 	at org.apache.cassandra.service.StorageProxy$8$1.runMayThrow(
> 	at org.apache.cassandra.service.StorageProxy$
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at

This message was sent by Atlassian JIRA

View raw message