ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Paschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5465) CREATE TABLE: add multithreaded tests
Date Wed, 14 Jun 2017 15:04:00 GMT

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

Alexander Paschenko commented on IGNITE-5465:
---------------------------------------------

Also such error may be seen when the previous error does not show up - despite the message,
this can happen both when client and server nodes initiate the query.

{code}
class org.apache.ignite.internal.processors.query.IgniteSQLException: Unexpected DDL operation
failure: Failed to start client cache (a cache with the given name is not started): SQL_PUBLIC_PERSON
	at org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:270)
	at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1331)
	at org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1845)
	at org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1841)
	at org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
	at org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2282)
	at org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1849)
	at org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest.executeSql(AbstractSchemaSelfTest.java:554)
	at org.apache.ignite.internal.processors.cache.index.H2DynamicTableConcurrentSelfTest.execute(H2DynamicTableConcurrentSelfTest.java:211)
	at org.apache.ignite.internal.processors.cache.index.H2DynamicTableConcurrentSelfTest.access$200(H2DynamicTableConcurrentSelfTest.java:44)
	at org.apache.ignite.internal.processors.cache.index.H2DynamicTableConcurrentSelfTest$1.call(H2DynamicTableConcurrentSelfTest.java:98)
	at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start client cache (a
cache with the given name is not started): SQL_PUBLIC_PERSON
	at org.apache.ignite.internal.processors.cache.ClusterCachesInfo.onCacheChangeRequested(ClusterCachesInfo.java:348)
	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.onCustomEvent(GridCacheProcessor.java:2879)
	at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:588)
	at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2387)
	at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processCustomMessage(ClientImpl.java:2293)
	at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1870)
	at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1754)
	at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{code}

> CREATE TABLE: add multithreaded tests
> -------------------------------------
>
>                 Key: IGNITE-5465
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5465
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Vladimir Ozerov
>            Assignee: Alexander Paschenko
>              Labels: important
>             Fix For: 2.1
>
>
> We need to add multithreaded tests for {{CREATE TABLE}} and {{DROP TABLE}} commands in
a similar way as we did that for indexes ({{DynamicIndexAbstractConcurrentSelfTest}}. 
> Let's test the following case:
> - Create and drop of the same several tables from different threads and different nodes
(including a client). 
> - Success criteria: nothing hangs and in the end table/cache is either doesn't exist,
or exists and operational (verify through DML and SELECT queries).
> AFAIK there is a bug in how we start caches dynamically, so honestly there is a high
chance that this test will not work as expected due to non-SQL bugs. So at the very least
we must ensure that it either works, or doesn't work due to a problem outside of DDL engine.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message