Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 21 Apr 2014 17:54:15 +0000 (UTC)
From: "Jason Brown (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12708354.1397503550259.148757.1398102855517@arcas>
In-Reply-To: <JIRA.12708354.1397503550259@arcas>
References: <JIRA.12708354.1397503550259@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-7033) new stress errors on reads
 with native protocol
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975779#comment-13975779 ] 

Jason Brown edited comment on CASSANDRA-7033 at 4/21/14 5:52 PM:
-----------------------------------------------------------------

Running with patch now and it looks likes it's working. However, as long as we're here, can you go ahead and see if you can eliminate this warning:

{code}WARN  17:49:28 Re-preparing already prepared query SELECT "C0","C1","C2","C3","C4" FROM "Standard1" WHERE KEY=?. Please note that preparing the same query more than once is generally an anti-pattern and will likely affect performance. Consider preparing the statement only once.{code}

It's printed once for for every thread that executes. and is kind of an annoyance when 913 threads are running :). Note: it happens on both reads and writes


was (Author: jasobrown):
Running with patch now and it looks likes it's working. However, as long as we're here, can you go ahead and see if you can eliminate this warning:

{info}WARN  17:49:28 Re-preparing already prepared query SELECT "C0","C1","C2","C3","C4" FROM "Standard1" WHERE KEY=?. Please note that preparing the same query more than once is generally an anti-pattern and will likely affect performance. Consider preparing the statement only once.{info}

It's printed once for for every thread that executes. and is kind of an annoyance when 913 threads are running :). Note: it happens on both reads and writes


> new stress errors on reads with native protocol
> -----------------------------------------------
>
>                 Key: CASSANDRA-7033
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7033
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jason Brown
>            Assignee: Benedict
>            Priority: Minor
>              Labels: native_protocol, stress
>             Fix For: 2.1
>
>         Attachments: 7033.txt
>
>
> Getting errors when performing reads on native protocol (possible due to using prepared statements). Generate writes with this:
> {code}
> cassandra-stress write -schema replication\(factor\=2\) -mode native prepared cql3 -port native=9043 thrift=9161 
> {code}
> Then trying to read gives this error:
> {code}
> cassandra-stress read -schema replication\(factor\=2\) -mode native prepared cql3 -port native=9043 thrift=9161  
> com.datastax.driver.core.exceptions.SyntaxError: line 1:7 no viable alternative at input '?'
> 	at com.datastax.driver.core.exceptions.SyntaxError.copy(SyntaxError.java:35)
> 	at com.datastax.driver.core.DefaultResultSetFuture.extractCauseFromExecutionException(DefaultResultSetFuture.java:256)
> 	at com.datastax.driver.core.SessionManager.prepare(SessionManager.java:110)
> 	at org.apache.cassandra.stress.util.JavaDriverClient.prepare(JavaDriverClient.java:57)
> 	at org.apache.cassandra.stress.operations.CqlOperation$JavaDriverWrapper.createPreparedStatement(CqlOperation.java:325)
> 	at org.apache.cassandra.stress.operations.CqlOperation.run(CqlOperation.java:74)
> 	at org.apache.cassandra.stress.operations.CqlOperation.run(CqlOperation.java:106)
> 	at org.apache.cassandra.stress.operations.CqlOperation.run(CqlOperation.java:269)
> 	at org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:296)
> Caused by: com.datastax.driver.core.exceptions.SyntaxError: line 1:7 no viable alternative at input '?'
> 	at com.datastax.driver.core.Responses$Error.asException(Responses.java:94)
> 	at com.datastax.driver.core.SessionManager$2.apply(SessionManager.java:209)
> 	at com.datastax.driver.core.SessionManager$2.apply(SessionManager.java:184)
> 	at com.google.common.util.concurrent.Futures$1.apply(Futures.java:713)
> 	at com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:861)
> 	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:722)
> {code}


--
This message was sent by Atlassian JIRA
(v6.2#6252)