Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 97AFC113D5 for ; Tue, 6 May 2014 16:02:24 +0000 (UTC) Received: (qmail 71332 invoked by uid 500); 6 May 2014 15:31:17 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 71304 invoked by uid 500); 6 May 2014 15:31:16 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 71286 invoked by uid 99); 6 May 2014 15:31:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 May 2014 15:31:16 +0000 Date: Tue, 6 May 2014 15:31:15 +0000 (UTC) From: "Mohica Jasha (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-7176) error in cassandra log file under stress MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990753#comment-13990753 ] Mohica Jasha commented on CASSANDRA-7176: ----------------------------------------- Unfortunately we didn't have our logging fully enabled by the time this happened. But from what I can see from logs the query just before the java-driver timeout occurred in the app-server most likely was {noformat} DELETE from conditional_update_lock where resource_id = '${myresourceid}' IF lock_id = ${myuuid}; {noformat} We cannot reproduce the problem. So I suspect maybe it is a race condition bug in Paxos implementation. Any idea? > error in cassandra log file under stress > ---------------------------------------- > > Key: CASSANDRA-7176 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7176 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Mohica Jasha > > We are using C* 2.0.5 with DC1:3, DC2:3 and datastax java-driver 2.0.1 in our app-server. > When we put our app-server under heavy stress testing. We got a {{com.datastax.driver.core.exceptions.ReadTimeoutException}} from java-driver and in the C* log file we got the following: > {noformat} > ERROR [Native-Transport-Requests:457009] 2014-05-02 13:49:09,794 QueryMessage.java (line 131) Unexpected error during query > java.lang.UnsupportedOperationException: Invalid consistency level: LOCAL_SERIAL > at org.apache.cassandra.db.ConsistencyLevel.blockFor(ConsistencyLevel.java:137) > at org.apache.cassandra.service.StorageProxy.beginAndRepairPaxos(StorageProxy.java:416) > at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:228) > at org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:423) > at org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:380) > at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:188) > at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:222) > at org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:119) > at org.apache.cassandra.transport.Message$Dispatcher.messageReceived(Message.java:304) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > 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) > ERROR [Native-Transport-Requests:457009] 2014-05-02 13:49:09,794 ErrorMessage.java (line 222) Unexpected exception during request > java.lang.UnsupportedOperationException: Invalid consistency level: LOCAL_SERIAL > at org.apache.cassandra.db.ConsistencyLevel.blockFor(ConsistencyLevel.java:137) > at org.apache.cassandra.service.StorageProxy.beginAndRepairPaxos(StorageProxy.java:416) > at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:228) > at org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:423) > at org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:380) > at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:188) > at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:222) > at org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:119) > at org.apache.cassandra.transport.Message$Dispatcher.messageReceived(Message.java:304) > at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) > at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.2#6252)