cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From João Silva (JIRA) <>
Subject [jira] [Commented] (CASSANDRA-13438) Got "InvalidQueryException: unconfigured table" when preparing statement after creating table
Date Wed, 12 Apr 2017 18:14:41 GMT


João Silva commented on CASSANDRA-13438:

The current "solution" for this problem is to sleep for 1s if the prepare statement call fails
with InvalidQueryException and retry this call. Using this fix the test program was able to
terminate successfully creating the 500 tables. This worked for all "reproduced in" server
versions and for Java driver 3.0.0 and 3.2.0.

Not sure what you want to do with this issue so I'll leave it open since this should have
a proper solution.

> Got "InvalidQueryException: unconfigured table" when preparing statement after creating
> ---------------------------------------------------------------------------------------------
>                 Key: CASSANDRA-13438
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         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
>         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.
> 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.
> 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

View raw message