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

Tyler Hobbs commented on CASSANDRA-6592:
----------------------------------------

+1 on the rebase of the 2.0 patch.  I've run my repro script for 5x the max 
time it took me to reproduce before with no errors.

Just to add more details for posterity, this was the schema:

{noformat}
CREATE TABLE duration_test.ints (key int, copy int, value int, RIMARY KEY (key, 
copy))
{noformat}

The statement that triggered the IllegalArgumentException was this:

{noformat}
DELETE FROM duration_test.ints USING TIMESTAMP 123456 WHERE key=? AND copy=?;
{noformat}

with the internal representation:
{noformat}
DeleteStatement(name=duration_test.ints, columns=[], keys=[key EQ ?, copy EQ ?]
{noformat}

Here are some of the negative sizes that statement got:  -20936, -25872, 
-19856, -4784, -16152.  (When reproducing to test this ticket, I never saw the 
large positive sizes, so that might have been a driver error, I suppose.)  
Typically the IAE's would come in bursts of ~5 within a second, and then it 
would be several hours before the next round of errors.

The only other activity while this happened was preparation of some insert 
statements and execution of various selects, inserts, and deletes (both 
prepared and non-prepared).  There were no schema changes or anything like that.

> IllegalArgumentException when Preparing Statements
> --------------------------------------------------
>
>                 Key: CASSANDRA-6592
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6592
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Sylvain Lebresne
>            Priority: Critical
>             Fix For: 1.2.14, 2.0.5
>
>         Attachments: 6592-2.0.txt
>
>
> When preparing a lot of statements with the python native driver, I 
> occasionally get an error response with an error that corresponds to the 
> following stacktrace in the cassandra logs:
> {noformat}
> ERROR [Native-Transport-Requests:126] 2014-01-11 13:58:05,503 
> ErrorMessage.java (line 210) Unexpected exception during request
> java.lang.IllegalArgumentException
>         at 
> com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap.checkArgument(ConcurrentLinkedHashMap.java:259)
>         at 
> com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap$BoundedEntryWeigher.weightOf(ConcurrentLinkedHashMap.java:1448)
>         at 
> com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap.put(ConcurrentLinkedHashMap.java:764)
>         at 
> com.googlecode.concurrentlinkedhashmap.ConcurrentLinkedHashMap.put(ConcurrentLinkedHashMap.java:743)
>         at 
> org.apache.cassandra.cql3.QueryProcessor.storePreparedStatement(QueryProcessor.java:255)
>         at 
> org.apache.cassandra.cql3.QueryProcessor.prepare(QueryProcessor.java:221)
>         at 
> org.apache.cassandra.transport.messages.PrepareMessage.execute(PrepareMessage.java:77)
>         at 
> org.apache.cassandra.transport.Message$Dispatcher.messageReceived(Message.java:287)
>         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$Worker.runTask(ThreadPoolExecutor.java:895)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>         at java.lang.Thread.run(Thread.java:662)
> {noformat}
> Looking at the CLHM source, this means we're giving the statement a weight 
> that's less than 1.  I'll also note that these errors frequently happen in 
> clumps of 2 or 3 at a time.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to