cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8137) Prepared statement size overflow error
Date Wed, 18 Mar 2015 21:17:38 GMT

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

Philip Thompson commented on CASSANDRA-8137:
--------------------------------------------

[~kishkaru], has this reproduced when running the duration tests on 2.1.3?

> Prepared statement size overflow error
> --------------------------------------
>
>                 Key: CASSANDRA-8137
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8137
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Linux Mint 64 | C* 2.1.0 | Ruby-driver master
>            Reporter: Kishan Karunaratne
>             Fix For: 2.1.4
>
>
> When using C* 2.1.0 and Ruby-driver master, I get the following error when running the
Ruby duration test (which prepares a lot of statements, in many threads):
> {noformat}
> Prepared statement of size 4451848 bytes is larger than allowed maximum of 2027520 bytes.
> Prepared statement of size 4434568 bytes is larger than allowed maximum of 2027520 bytes.
> {noformat}
> They usually occur in batches of 1, but sometimes in multiples as seen above.  It happens
occasionally, around 20% of the time when running the code.  Unfortunately I don't have a
stacktrace as the error isn't recorded in the system log. 
> This is my schema, and the offending prepare statement:
> {noformat}
> @session.execute("CREATE TABLE duration_test.ints (
>                         key INT,
>                         copy INT,
>                         value INT,
>                         PRIMARY KEY (key, copy))"
> )
> {noformat}
> {noformat}
> select = @session.prepare("SELECT * FROM ints WHERE key=?")
> {noformat}
> Now, I notice that if I explicitly specify the keyspace in the prepare, I don't get the
error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message