You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Suntsov (JIRA)" <ji...@apache.org> on 2018/08/29 11:04:00 UTC
[jira] [Created] (IGNITE-9417)
IgniteSqlInsertIndexedValueBenchamrks failed with more than one driver
Ilya Suntsov created IGNITE-9417:
------------------------------------
Summary: IgniteSqlInsertIndexedValue<N>Benchamrks failed with more than one driver
Key: IGNITE-9417
URL: https://issues.apache.org/jira/browse/IGNITE-9417
Project: Ignite
Issue Type: Bug
Reporter: Ilya Suntsov
I guess that we need to handle errors like bellow and continue to work OR each driver must insert it's own key range:
{noformat}
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
javax.cache.CacheException: Duplicate key during INSERT [key=52]
<------>at org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:676)
<------>at org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:615)
<------>at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:385)
<------>at org.apache.ignite.yardstick.cache.dml.IgniteSqlInsertIndexedValue1Benchmark.test(IgniteSqlInsertIndexedValue1Benchmark.java:38)
<------>at org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178)
<------>at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.internal.processors.query.IgniteSQLException: Duplicate key during INSERT [key=52]
<------>at org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:803)
<------>at org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.processDmlSelectResult(DmlStatementsProcessor.java:581)
<------>at org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:539)
<------>at org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:171)
<------>at org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:345)
<------>at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1791)
<------>at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1755)
<------>at org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2107)
<------>at org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2102)
<------>at org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
<------>at org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2650)
<------>at org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2116)
<------>at org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:664)
<------>... 5 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)