You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/19 01:54:00 UTC
[jira] [Updated] (CASSANDRA-13438) Got "InvalidQueryException:
unconfigured table" when preparing statement after creating table
[ https://issues.apache.org/jira/browse/CASSANDRA-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-13438:
-----------------------------------------
Component/s: CQL
> Got "InvalidQueryException: unconfigured table" when preparing statement after creating table
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-13438
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13438
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Environment: Host: Ubuntu 16.04.1 LTS, jdk 1.8.0_60-b27, docker 1.11.2 and cassandra DataStax Java driver 3.0.0.
> The client program runs on the host and the cassandra cluster runs on docker using the official docker cassandra image (multiple versions, see the reproduced in field).
> Reporter: João Silva
> Priority: Major
> Attachments: cassandra_add_table.tar.gz
>
>
> I get the InvalidQueryException: unconfigured columnfamily (or table, depending of the server version) when trying to prepare an insert statement right after creating the table. This behavior is not deterministic but by running the attached program the problem occurs almost always.
> First I start a 3 node cassandra cluster (RF=3) using the docker cassandra image. Then a client Java program, using driver 3.0.0, starts 50 threads each one creating 1 table (synchronously) and preparing an insert statement for it (repeating this 10x for each thread). Eventually the exception occurs.
> *Important:*
> - I'm checking for schema agreement when creating the table and it seems to be achieving it successfully. The schema agreement timeout was increased to 2 minutes.
> - This are *not* concurrent schema changes.
> Note that this is an extreme table creation test scenario to make the problem more evident.
> See the README file in the attachment for instructions on how to start the cluster and run the program.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org