AssertionError as a result of a timeout

[Ben Hood <0x...@gmail.com>]

Hi all,

This is just a follow up to say that this issue is being tracked here:

https://issues.apache.org/jira/browse/CASSANDRA-6796

I managed to work around this issue for my workload by increasing the
write timeout threshold in the server, but YMMV.

Sorry that the original list thread had an empty subject :-(

Cheers,

Ben

On Wed, Apr 9, 2014 at 11:34 AM, Ben Hood <0x...@gmail.com> wrote:
> Hi all,
>
> I'm getting the following error in a 2.0.6 instance:
>
> ERROR [Native-Transport-Requests:16633] 2014-04-09 10:11:45,811
> ErrorMessage.java (line 222) Unexpected exception during request
> java.lang.AssertionError: localhost/127.0.0.1
> at org.apache.cassandra.service.StorageProxy.submitHint(StorageProxy.java:860)
> at org.apache.cassandra.service.StorageProxy.mutate(StorageProxy.java:480)
> at org.apache.cassandra.service.StorageProxy.mutateWithTriggers(StorageProxy.java:524)
> at org.apache.cassandra.cql3.statements.BatchStatement.executeWithoutConditions(BatchStatement.java:210)
> at org.apache.cassandra.cql3.statements.BatchStatement.execute(BatchStatement.java:203)
> at org.apache.cassandra.cql3.statements.BatchStatement.executeWithPerStatementVariables(BatchStatement.java:192)
> at org.apache.cassandra.cql3.QueryProcessor.processBatch(QueryProcessor.java:373)
> at org.apache.cassandra.transport.messages.BatchMessage.execute(BatchMessage.java:206)
> at org.apache.cassandra.transport.Message$Dispatcher.messageReceived(Message.java:304)
> at org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.doRun(ChannelUpstreamEventRunnable.java:43)
> at org.jboss.netty.handler.execution.ChannelEventRunnable.run(ChannelEventRunnable.java:67)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
>
> Looking at the source for this, it appears to be related to a timeout:
>
> // local write that time out should be handled by LocalMutationRunnable
> assert !target.equals(FBUtilities.getBroadcastAddress()) : target;
>
> Cursory testing indicates that this occurs during larger batch ingests.
>
> But the error does not appear to be propagated properly back to the
> client and it seems like this could be due to some misconfiguration.
>
> Has anybody seen something like this before?
>
> Cheers,
>
> Ben