[jira] [Created] (IGNITE-14443) Calcite integration. SqlFirstLastValueAggFunction support
Pavel Vinokurov created IGNITE-14443: Summary: Calcite integration. SqlFirstLastValueAggFunction support Key: IGNITE-14443 URL: https://issues.apache.org/jira/browse/IGNITE-14443 Project: Ignite Issue Type: New Feature Components: sql Affects Versions: 3.0.0-alpha1 Reporter: Pavel Vinokurov We need to support aggregation functions, especially SqlFirstLastValueAggFunction that allows simplify and optimize the wide range of sql queries. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14439) NPE when accessing clustername before first exchange finished
Pavel Vinokurov created IGNITE-14439: Summary: NPE when accessing clustername before first exchange finished Key: IGNITE-14439 URL: https://issues.apache.org/jira/browse/IGNITE-14439 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.9 Reporter: Pavel Vinokurov [IGNITE-11406|https://issues.apache.org/jira/browse/IGNITE-11406] has not been fixed properly for two reasons. The first is one is that _GridCacheProcessor.utilityCache_ could be accessed before the first exchange finished. The second is that it doesn't resolve the original issue, because _GridServiceProcessor.onKernelStop_ is followed by _GridCacheProcessor.onKernelStop_, so caches should be already initialized. Thus that fix should be reverted. Revering this fix induces the issue related to accessing the utility cache by getting cluster name. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14263) Failure handler is triggered by NPE on unstable topology
Pavel Vinokurov created IGNITE-14263:
Summary: Failure handler is triggered by NPE on unstable topology
Key: IGNITE-14263
URL: https://issues.apache.org/jira/browse/IGNITE-14263
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9.1
Reporter: Pavel Vinokurov
Attachments: Reproducer.java
Restarting servers and clients produced the following exception:
{code:java}
SEVERE: Critical system error detected. Will be handled accordingly to
configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class
o.a.i.IgniteCheckedException: null]]
class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7759)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:268)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:217)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:168)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3222)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.ownOrphans(GridDhtPartitionTopologyImpl.java:2075)
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.onExchangeDone(GridDhtPartitionTopologyImpl.java:2059)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2535)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:159)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:475)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8.run(GridDhtPartitionsExchangeFuture.java:5119)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initDone(GridDhtPartitionsExchangeFuture.java:5002)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.clientOnlyExchange(GridDhtPartitionsExchangeFuture.java:1592)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:1052)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3403)
... 3 more
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14256) SQL delete statement ignores skipOnReduce and local flags for replicated caches
Pavel Vinokurov created IGNITE-14256:
Summary: SQL delete statement ignores skipOnReduce and local flags
for replicated caches
Key: IGNITE-14256
URL: https://issues.apache.org/jira/browse/IGNITE-14256
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.9.1
Reporter: Pavel Vinokurov
Delete statement removes data from all nodes ignoring enabled lazy and
skipOnReduce flags.
The reproducer is attached.
Below the stacktrace
{code:java}
"sys-stripe-4-#68%5f5ea90d-6614-448f-9df7-0d770f0b216d%" #111 prio=5 os_prio=0
tid=0x7fbac1d59000 nid=0x7329 runnable [0x7fba8c7ed000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.EPollArrayWrapper.interrupt(Native Method)
at sun.nio.ch.EPollArrayWrapper.interrupt(EPollArrayWrapper.java:317)
at sun.nio.ch.EPollSelectorImpl.wakeup(EPollSelectorImpl.java:207)
- locked <0x0005cc4475f8> (a java.lang.Object)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.offer(GridNioServer.java:1988)
at
org.apache.ignite.internal.util.nio.GridNioServer.send0(GridNioServer.java:652)
at
org.apache.ignite.internal.util.nio.GridNioServer.send(GridNioServer.java:620)
at
org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onSessionWrite(GridNioServer.java:3704)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedSessionWrite(GridNioFilterAdapter.java:120)
at
org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onSessionWrite(GridConnectionBytesVerifyFilter.java:80)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedSessionWrite(GridNioFilterAdapter.java:120)
at
org.apache.ignite.internal.util.nio.GridNioCodecFilter.onSessionWrite(GridNioCodecFilter.java:90)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedSessionWrite(GridNioFilterAdapter.java:120)
at
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onSessionWrite(GridNioFilterChain.java:268)
at
org.apache.ignite.internal.util.nio.GridNioFilterChain.onSessionWrite(GridNioFilterChain.java:191)
at
org.apache.ignite.internal.util.nio.GridNioSessionImpl.sendNoFuture(GridNioSessionImpl.java:129)
at
org.apache.ignite.internal.util.nio.GridTcpNioCommunicationClient.sendMessage(GridTcpNioCommunicationClient.java:115)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1182)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1124)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1809)
at
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1923)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1257)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1296)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.sendDhtRequests(GridDhtAtomicAbstractUpdateFuture.java:489)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:445)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1926)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1679)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:3190)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:151)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:286)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:281)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
at
[jira] [Created] (IGNITE-13989) Destroy of persisted cache doesn't remove cache folder
Pavel Vinokurov created IGNITE-13989: Summary: Destroy of persisted cache doesn't remove cache folder Key: IGNITE-13989 URL: https://issues.apache.org/jira/browse/IGNITE-13989 Project: Ignite Issue Type: Bug Affects Versions: 2.9.1 Reporter: Pavel Vinokurov IgniteCache#destroy doesn't remove the folder in the persistent storage. Creating/Destroying dynamic caches could clutter the PDS and meet with the system limits -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13960) Starvation in mgmt pool caused by MetadataTask execution
Pavel Vinokurov created IGNITE-13960:
Summary: Starvation in mgmt pool caused by MetadataTask execution
Key: IGNITE-13960
URL: https://issues.apache.org/jira/browse/IGNITE-13960
Project: Ignite
Issue Type: Bug
Components: compute
Affects Versions: 2.9.1
Reporter: Pavel Vinokurov
Assignee: Pavel Vinokurov
*Issue:*
Requesting cache metadata from multiple threads causes starvation in the mgmt
pool.
*Root Cause:*
>From the mgmt pool GridCacheCommandHandler.MetadataJob calls
>GridCacheQueryManager#sqlMetadata() and
>GridClosureProcessor#callAsyncNoFailover().get() that executes and waits an
>another internal task. The job response of this task should be also handled
>from the mgmt pool. It causes starvation.
*Proposed Fix:*
Make GridCacheQueryManager#sqlMetadata() asynchronous and apply continuation
for GridCacheCommandHandler.MetadataJob to release a mgmt thread for the time
of completing the future returned by sqlMetadata().
Attached threads with hanging threads:
{code:java}
"mgmt-#10633" #14311 prio=5 os_prio=0 tid=0x560c79117000 nid=0x134c6
waiting on condition [0x7f15baa77000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.sqlMetadata(GridCacheQueryManager.java:1803)
at
org.apache.ignite.internal.processors.rest.handlers.cache.GridCacheCommandHandler$MetadataJob.execute(GridCacheCommandHandler.java:1123)
at
org.apache.ignite.internal.processors.rest.handlers.cache.GridCacheCommandHandler$MetadataJob.execute(GridCacheCommandHandler.java:1088)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:567)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7069)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:561)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:490)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1270)
at
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:2088)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1635)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1255)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4300(GridIoManager.java:144)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.execute(GridIoManager.java:1144)
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:50)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
"mgmt-#81" #270 prio=5 os_prio=0 tid=0x562323c3c800 nid=0x592 waiting on
condition [0x7fba5f378000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor$ClientChangeGlobalStateComputeRequest.run(GridClusterStateProcessor.java:1979)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C4.execute(GridClosureProcessor.java:1943)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:567)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7069)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:561)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:490)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1270)
at
[jira] [Created] (IGNITE-13792) Reconnecting clients trigger failure handler
Pavel Vinokurov created IGNITE-13792:
Summary: Reconnecting clients trigger failure handler
Key: IGNITE-13792
URL: https://issues.apache.org/jira/browse/IGNITE-13792
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.9
Reporter: Pavel Vinokurov
Attachments: UnstableClients.java
{code:java}
Dec 01, 2020 9:38:29 PM java.util.logging.LogManager$RootLogger log
SEVERE: JVM will be halted immediately due to the failure:
[failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class
o.a.i.IgniteCheckedException: Affinity for topology version is not initialized
[locNode=b50635ff-0324-431b-bc34-00a6cd36c9e3, grp=ignite-sys-cache,
topVer=AffinityTopologyVersion [topVer=570, minorTopVer=0],
head=AffinityTopologyVersion [topVer=569, minorTopVer=0],
history=[AffinityTopologyVersion [topVer=551, minorTopVer=0],
AffinityTopologyVersion [topVer=552, minorTopVer=0], AffinityTopologyVersion
[topVer=553, minorTopVer=0], AffinityTopologyVersion [topVer=554,
minorTopVer=0], AffinityTopologyVersion [topVer=555, minorTopVer=0],
AffinityTopologyVersion [topVer=556, minorTopVer=0], AffinityTopologyVersion
[topVer=557, minorTopVer=0], AffinityTopologyVersion [topVer=558,
minorTopVer=0], AffinityTopologyVersion [topVer=559, minorTopVer=0],
AffinityTopologyVersion [topVer=560, minorTopVer=0], AffinityTopologyVersion
[topVer=561, minorTopVer=0], AffinityTopologyVersion [topVer=562,
minorTopVer=0], AffinityTopologyVersion [topVer=563, minorTopVer=0],
AffinityTopologyVersion [topVer=564, minorTopVer=0], AffinityTopologyVersion
[topVer=565, minorTopVer=0], AffinityTopologyVersion [topVer=566,
minorTopVer=0], AffinityTopologyVersion [topVer=567, minorTopVer=0],
AffinityTopologyVersion [topVer=568, minorTopVer=0], AffinityTopologyVersion
[topVer=569, minorTopVer=0]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13791) NullPointerException when topology is unstable
Pavel Vinokurov created IGNITE-13791:
Summary: NullPointerException when topology is unstable
Key: IGNITE-13791
URL: https://issues.apache.org/jira/browse/IGNITE-13791
Project: Ignite
Issue Type: Bug
Components: networking
Affects Versions: 2.9.1
Reporter: Pavel Vinokurov
Attachments: UnstableServerTopology.java
Unstable topology with blinking server nodes leads to the critical system error:
{code:java}
SEVERE: Critical system error detected. Will be handled accordingly to
configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]]
java.lang.NullPointerException
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:5096)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:3236)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2915)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:8064)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:3086)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7995)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:58)
Dec 01, 2020 8:22:55 PM java.util.logging.LogManager$RootLogger log
SEVERE: JVM will be halted immediately due to the failure:
[failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION,
err=java.lang.NullPointerException]]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13649) Local cache causes system thread pool overflow
Pavel Vinokurov created IGNITE-13649: Summary: Local cache causes system thread pool overflow Key: IGNITE-13649 URL: https://issues.apache.org/jira/browse/IGNITE-13649 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.8.1 Reporter: Pavel Vinokurov Attachments: LocalCacheAndStoreReproducerClient.java, LocalCacheAndStoreReproducerServer.java Calling get operations for a LOCAL cache with read-through within a long running job causes system thread pool overflow. Scenario: 1. Start 2 server nodes using LocalCacheAndStoreReproducerServer 2. Start 1 client node using LocalCacheAndStoreReproducerClient 3. Forcible stop the client node. Result: The system thread pool is consistently increasing until OOM. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13632) Transaction hangs due to communication failures
Pavel Vinokurov created IGNITE-13632: Summary: Transaction hangs due to communication failures Key: IGNITE-13632 URL: https://issues.apache.org/jira/browse/IGNITE-13632 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.8.1 Reporter: Pavel Vinokurov Attachments: TxReproducer.java Transaction hangs after dropping communication messages. The reproducer is attached -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13507) Critical error on tx recovery
Pavel Vinokurov created IGNITE-13507:
Summary: Critical error on tx recovery
Key: IGNITE-13507
URL: https://issues.apache.org/jira/browse/IGNITE-13507
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.7.5
Reporter: Pavel Vinokurov
Server node failed because of NullPointerException on tx recovery:
{code:java}
[17:15:02,428][SEVERE][sys-#305][] Critical system error detected. Will be
handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler
[tryStop=false, timeout=0, super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=CRITICAL_ERROR, err=class o.a.i.IgniteException: Failed to perform tx
recovery]]
class org.apache.ignite.IgniteException: Failed to perform tx recovery
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$TxRecoveryInitRunnable.run(IgniteTxManager.java:3288)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7186)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:826)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.IgniteFeatures.nodeSupports(IgniteFeatures.java:212)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$TxRecoveryInitRunnable.isMvccRecoveryMessageRequired(IgniteTxManager.java:3304)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$TxRecoveryInitRunnable.run(IgniteTxManager.java:3208)
... 6 more
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13439) Printing detailed classpath slowdowns node initialization
Pavel Vinokurov created IGNITE-13439: Summary: Printing detailed classpath slowdowns node initialization Key: IGNITE-13439 URL: https://issues.apache.org/jira/browse/IGNITE-13439 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.8.1 Reporter: Pavel Vinokurov If IGNITE_LOG_CLASSPATH_CONTENT_ON_STARTUP is enabled, IgniteKernel#ackClassPathContent parses the classpath and recursively traverses the file system printing all jars and class files. Traversing the files system could take much time in case of many class files or having a root folder in the classpath. The reasonable behavior is to print only root classpath folders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13000) Connection.prepareStatement(String,int) always throws UnsupportedException ignoring 'autoGeneratedKeys' parameter
Pavel Vinokurov created IGNITE-13000:
Summary: Connection.prepareStatement(String,int) always throws
UnsupportedException ignoring 'autoGeneratedKeys' parameter
Key: IGNITE-13000
URL: https://issues.apache.org/jira/browse/IGNITE-13000
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.8
Reporter: Pavel Vinokurov
Below the method call throwing Exception.
{code:java}
conn.prepareStatement(query, Statement.NO_GENERATED_KEYS)
{code}
But there is should be the same result as for:
{code:java}
conn.prepareStatement(query)
{code}
The possible fix:
{code:java}
@Override
public PreparedStatement prepareStatement(String sql, int autoGeneratedKeys)
throws SQLException {
ensureNotClosed();
if(autoGeneratedKeys == Statement.RETURN_GENERATED_KEYS)
throw new SQLFeatureNotSupportedException("Auto generated keys are not
supported.");
return prepareStatement(sql);
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-11798) Memory leak on unstable topology caused by reservation partitions
Pavel Vinokurov created IGNITE-11798: Summary: Memory leak on unstable topology caused by reservation partitions Key: IGNITE-11798 URL: https://issues.apache.org/jira/browse/IGNITE-11798 Project: Ignite Issue Type: Bug Components: cache, sql Reporter: Pavel Vinokurov Attachments: PartitionReservationReproducer.java Executing queries on unstable topology leads to OOM caused by leak of the partition reservation. The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11699) Node can't start after forced shutdown if the wal archiver disabled
Pavel Vinokurov created IGNITE-11699:
Summary: Node can't start after forced shutdown if the wal
archiver disabled
Key: IGNITE-11699
URL: https://issues.apache.org/jira/browse/IGNITE-11699
Project: Ignite
Issue Type: Bug
Components: persistence
Affects Versions: 2.7
Reporter: Pavel Vinokurov
If a server node killed with the disabled wal archive, it could fail on start
with following exception:
{code:java}
[18:37:53,887][SEVERE][sys-stripe-1-#2][G] Failed to execute runnable.
java.lang.IllegalStateException: Failed to get page IO instance (page content
is corrupted)
at
org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:85)
at
org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:97)
at
org.apache.ignite.internal.pagemem.wal.record.delta.MetaPageUpdatePartitionDataRecord.applyDelta(MetaPageUpdatePartitionDataRecord.java:109)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyPageDelta(GridCacheDatabaseSharedManager.java:2532)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$performBinaryMemoryRestore$11(GridCacheDatabaseSharedManager.java:2327)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$stripedApplyPage$12(GridCacheDatabaseSharedManager.java:2441)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$stripedApply$13(GridCacheDatabaseSharedManager.java:2479)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:550)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{code}
The reproducer is attached(works only on Linux).
Steps to run the reproducer.
1. Copy config/server.xml into IGNITE_HOME/config folder;
2. Set IGNITE_HOME in the CorruptionReproducer class;
3. Launch CorruptionReproducer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11585) Update Spring dependency to version 5
Pavel Vinokurov created IGNITE-11585: Summary: Update Spring dependency to version 5 Key: IGNITE-11585 URL: https://issues.apache.org/jira/browse/IGNITE-11585 Project: Ignite Issue Type: Improvement Reporter: Pavel Vinokurov Assignee: Pavel Vinokurov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11544) Unclear behavior for cache operations using classes different from specified as indexed types
Pavel Vinokurov created IGNITE-11544: Summary: Unclear behavior for cache operations using classes different from specified as indexed types Key: IGNITE-11544 URL: https://issues.apache.org/jira/browse/IGNITE-11544 Project: Ignite Issue Type: Bug Components: cache, sql Affects Versions: 2.7 Reporter: Pavel Vinokurov Attachments: IndexedTypesReproducer.java There are a few cases presented in the attached reproducer where caches are populated by objects of classes different from specified in CacheConfiguration#setIndexedTypes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11524) Memory leak caused by executing an jdbc prepared statement
Pavel Vinokurov created IGNITE-11524: Summary: Memory leak caused by executing an jdbc prepared statement Key: IGNITE-11524 URL: https://issues.apache.org/jira/browse/IGNITE-11524 Project: Ignite Issue Type: Bug Components: sql, thin client Reporter: Pavel Vinokurov Fix For: 2.7 Attachments: PreparedStatementOOMReproducer.java Executing a prepared statement multiple times lead to OOM. VisualVM indicates that heap contains a lot of JdbcThinPreparedStatament objects. The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11419) Memory leak after multiple restarts of server node within the same jvm
Pavel Vinokurov created IGNITE-11419: Summary: Memory leak after multiple restarts of server node within the same jvm Key: IGNITE-11419 URL: https://issues.apache.org/jira/browse/IGNITE-11419 Project: Ignite Issue Type: Bug Reporter: Pavel Vinokurov Multiple restarts of a server node with enabled persistence and 20 caches lead to OutOfMemory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11383) Unable to restart node with WALMode.NONE
Pavel Vinokurov created IGNITE-11383:
Summary: Unable to restart node with WALMode.NONE
Key: IGNITE-11383
URL: https://issues.apache.org/jira/browse/IGNITE-11383
Project: Ignite
Issue Type: Bug
Components: persistence
Affects Versions: 2.7
Reporter: Pavel Vinokurov
Attachments: MemoryRestoreReproducer.java
Scenario:
1. Start single node with persistence without WAL.
2. Stream data to a cache.
3. Restart the node.
Result:
Node failed with following exception.
{code:java}
Exception in thread "main" class org.apache.ignite.IgniteException: null
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1059)
at org.apache.ignite.Ignition.start(Ignition.java:324)
at MemoryRestoreReproducer.main(MemoryRestoreReproducer.java:27)
Caused by: class org.apache.ignite.IgniteCheckedException: null
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1196)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1992)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1683)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1109)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:629)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:554)
at org.apache.ignite.Ignition.start(Ignition.java:321)
... 1 more
Caused by: java.util.NoSuchElementException
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:39)
at
org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:35)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.read(FileWriteAheadLogManager.java:855)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.performBinaryMemoryRestore(GridCacheDatabaseSharedManager.java:2120)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:749)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:4963)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1058)
... 7 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11378) Critical system errors on cluster with enabled peristance
Pavel Vinokurov created IGNITE-11378: Summary: Critical system errors on cluster with enabled peristance Key: IGNITE-11378 URL: https://issues.apache.org/jira/browse/IGNITE-11378 Project: Ignite Issue Type: Bug Components: persistence Reporter: Pavel Vinokurov Attachments: CheckpointLockReproducer.java The attached reproducer shows the following exception during streaming data to cache: [2019-02-21 16:15:23,202][ERROR][tcp-disco-msg-worker-[100a6976 0:0:0:0:0:0:0:1%lo:47500]-#19%3%][root] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet []]], failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker [name=data-streamer-stripe-5, igniteInstanceName=3, finished=false, heartbeatTs=1550754912905]]] class org.apache.ignite.IgniteException: GridWorker [name=data-streamer-stripe-5, igniteInstanceName=3, finished=false, heartbeatTs=1550754912905] If the blocked timeout is changed by cfg.setSystemWorkerBlockedTimeout(30_000), after streaming data and restarting several nodes the following critical error occurs: [2019-02-21 16:24:07,164][ERROR][grid-timeout-worker-#214%client%][G] Blocked system-critical thread has been detected. This can lead to cluster-wide undefined behaviour [threadName=tcp-comm-worker, blockedFor=36s] [2019-02-21 16:24:07,166][WARN ][grid-timeout-worker-#214%client%][G] Thread [name="tcp-comm-worker-#25%client%", id=482, state=TIMED_WAITING, blockCnt=0, waitCnt=729] [2019-02-21 16:24:07,168][ERROR][grid-timeout-worker-#214%client%][root] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet []]], failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker [name=tcp-comm-worker, igniteInstanceName=client, finished=false, heartbeatTs=1550755410331]]] class org.apache.ignite.IgniteException: GridWorker [name=tcp-comm-worker, igniteInstanceName=client, finished=false, heartbeatTs=1550755410331] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10873) CorruptedTreeException during simultaneous cache put operations
Pavel Vinokurov created IGNITE-10873: Summary: CorruptedTreeException during simultaneous cache put operations Key: IGNITE-10873 URL: https://issues.apache.org/jira/browse/IGNITE-10873 Project: Ignite Issue Type: Bug Components: cache, persistence Affects Versions: 2.7 Reporter: Pavel Vinokurov [2019-01-09 20:47:04,376][ERROR][pool-9-thread-9][GridDhtAtomicCache] Unexpected exception during cache update org.h2.message.DbException: General error: "class org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException: Runtime failure on row: Row@780acfb4[ key: model.TbclsrInputKey [idHash=1823856383, hash=275143246, clsbInputRef=GTEST, firstInputFlag=254], val: model.TbclsrInput [idHash=708235920, hash=-19147671, clsbMatchRef=null, origBic=null, desStlmtMbrBic=null, cpBic=null, cpDesSmBic=null, desSmManuAuth=0, origRef=null, relatedRef=null, commonRef=null, clsbTransRef=null, lastAmdSendRef=null, branchId=null, inputType=null, formatType=0, sourceType=0, sourceId=0, operType=null, fwdBookFlag=0, possDupFlag=0, sameDayFlag=0, pendingFlag=0, rescOrigSmFlag=0, rescCpCpsmFlag=0, stlmtEligFlag=0, authTms=null, ntfId=0, inputStatus=0, lastActionTms=null, ofacStatus=0, ofacTms=null, prevInputStatus=0, prevTms=null, cpOfacStatus=0, sentDt=null, valueDt=null, tradeDt=null, origSuspFlag=0, origSmSuspFlag=0, cpSuspFlag=0, cpSmSuspFlag=0, currSuspFlag=0, tpIndicatorFlag=0, tpBic=null, tpReference=null, tpFreeText=null, tpFurtherRef=null, tpCustIntRef=null, tpMbrField1=null, tpMbrField2=null, exchRate=0.0, currIdBuy=0, volBuy=0.0, currIdSell=0, volSell=0.0, inputVersionId=0, versionId=null, grpQueueOrderNo=0, queueOrderNo=0, originalGroupId=0, groupStatus=0, usi=null, prevUsi=null, origLei=null, cpLei=null, fundLei=null, reportJuris=null, execVenue=null, execTms=null, execTmsUtcoff=null, mappingRule=null, reportJuris2=null, usi2=null, prevUsi2=null, reportJuris3=null, usi3=null, prevUsi3=null], ver: GridCacheVersion [topVer=158536014, order=1547056011256, nodeOrder=1] ][ GTEST, null, 254, null, null, null, null, 0, null, null, null, null, null, null, null, 0, 0, 0, null, 0, 0, 0, 0, 0, 0, 0, null, 0, 0, null, 0, null, 0, null, 0, null, null, null, 0, 0, 0, 0, 0, 0, null, null, null, null, null, null, null, 0.0, 0, 0.0, 0, 0.0, 0, null, 0, 0, 0, 0, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null ]" [5-197] at org.h2.message.DbException.get(DbException.java:168) at org.h2.message.DbException.convert(DbException.java:307) at org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:302) at org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.addToIndex(GridH2Table.java:546) at org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:479) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:768) at org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1905) at org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:404) at org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2633) at org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1646) at org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1621) at org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1935) at org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:428) at org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2295) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2494) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1951) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1780) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1668) at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
[jira] [Created] (IGNITE-10524) IgniteCache.iterator() from a client node leads to OOM
Pavel Vinokurov created IGNITE-10524: Summary: IgniteCache.iterator() from a client node leads to OOM Key: IGNITE-10524 URL: https://issues.apache.org/jira/browse/IGNITE-10524 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.4 Reporter: Pavel Vinokurov Looks like "iterator()" method perform a scan query and load all cache rows into heap. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10291) Unable to find row by index created on partial baseline topology
Pavel Vinokurov created IGNITE-10291: Summary: Unable to find row by index created on partial baseline topology Key: IGNITE-10291 URL: https://issues.apache.org/jira/browse/IGNITE-10291 Project: Ignite Issue Type: Bug Components: cache, sql Affects Versions: 2.6, 2.5, 2.4 Reporter: Pavel Vinokurov Attachments: Reproducer.java Steps to reproduce: 1. Start two nodes cluster with persistence. 2. Create table CREATE TABLE PERSON ( FIRST_NAME VARCHAR, LAST_NAME VARCHAR, ADDRESS VARCHAR, LANG VARCHAR, BIRTH_DATE TIMESTAMP, CONSTRAINT PK_PESON PRIMARY KEY (FIRST_NAME,LAST_NAME,ADDRESS,LANG) ) WITH "key_type=PersonKeyType, CACHE_NAME=PersonCache, value_type=PersonValueType, AFFINITY_KEY=FIRST_NAME,template=PARTITIONED,backups=1" Insert 1000 rows. 3. Stop the second node. 4. Create index create index PERSON_FIRST_NAME_IDX on PERSON(FIRST_NAME) 5. Start the second node 6. Perform select query for each row: select * from PERSON use index(PERSON_FIRST_NAME_IDX) where FIRST_NAME=? and LAST_NAME=? and ADDRESS=? and LANG = ? Result: The select doesn't return row in half of cases. The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10110) SQL query with DISTINCT and JOIN in suquery produces "Column not found"
Pavel Vinokurov created IGNITE-10110: Summary: SQL query with DISTINCT and JOIN in suquery produces "Column not found" Key: IGNITE-10110 URL: https://issues.apache.org/jira/browse/IGNITE-10110 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.4 Reporter: Pavel Vinokurov Initial script: CREATE TABLE Person( person_id INTEGER PRIMARY KEY, company_id INTEGER, last_name VARCHAR(100) ); CREATE TABLE Company( company_id INTEGER PRIMARY KEY, location_id INTEGER ); CREATE TABLE Department( department_id INTEGER PRIMARY KEY, person_id INTEGER ); CREATE TABLE Organization( organization_id INTEGER PRIMARY KEY, company_id INTEGER ); Query: SELECT last_name FROM ( SELECT last_name, person_id, company_id FROM ( SELECT last_name, person_id, p.company_id as company_id FROM Person p INNER JOIN ( SELECT DISTINCT location_id, company_id FROM Company WHERE location_id = 1 ) cpy ON ( p.company_id = cpy.company_id ) ) a ) src INNER JOIN department dep ON src.person_id = dep.person_id LEFT JOIN organization og ON src.company_id = og.company_id Result: Caused by: org.h2.jdbc.JdbcSQLException: Column "SRC__Z4.COMPANY_ID" not found; SQL statement: SELECT DEP__Z5.PERSON_ID __C2_0 FROM PUBLIC.DEPARTMENT DEP__Z5 LEFT OUTER JOIN PUBLIC.ORGANIZATION OG__Z6 ON SRC__Z4.COMPANY_ID = OG__Z6.COMPANY_ID -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9626) Applying WAL updates ignores evicition policy
Pavel Vinokurov created IGNITE-9626: --- Summary: Applying WAL updates ignores evicition policy Key: IGNITE-9626 URL: https://issues.apache.org/jira/browse/IGNITE-9626 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Pavel Vinokurov Assignee: Pavel Vinokurov Attachments: IgniteExpirationWitPeristanceReproducer.java Steps to reproduce: 1. Add record for cache obtained by ignite.cache().withExpiryPolicy(). 2. Stops node before checkpoint. 3. Start node and get record for cache after specified duration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9550) Cache get operation returns null for a lost partition
Pavel Vinokurov created IGNITE-9550: --- Summary: Cache get operation returns null for a lost partition Key: IGNITE-9550 URL: https://issues.apache.org/jira/browse/IGNITE-9550 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.6 Reporter: Pavel Vinokurov Assignee: Pavel Vinokurov Attachments: PartitionLostReproducer.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9474) Ignite does not eagerly remove expired cache entries
Pavel Vinokurov created IGNITE-9474: --- Summary: Ignite does not eagerly remove expired cache entries Key: IGNITE-9474 URL: https://issues.apache.org/jira/browse/IGNITE-9474 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.4 Reporter: Pavel Vinokurov Attachments: IgniteExpirationReproducerWithoutPersistance.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9264) Lost partitions raised twice
Pavel Vinokurov created IGNITE-9264: --- Summary: Lost partitions raised twice Key: IGNITE-9264 URL: https://issues.apache.org/jira/browse/IGNITE-9264 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.4 Reporter: Pavel Vinokurov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9178) Partition lost event are not triggered if multiple nodes left cluster
Pavel Vinokurov created IGNITE-9178: --- Summary: Partition lost event are not triggered if multiple nodes left cluster Key: IGNITE-9178 URL: https://issues.apache.org/jira/browse/IGNITE-9178 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.4 Reporter: Pavel Vinokurov If multiple nodes left cluster simultaneously, left partitions are removed from GridDhtPartitionTopologyImpl#node2part without adding to leftNode2Part in GridDhtPartitionTopologyImpl#update method. Thus GridDhtPartitionTopologyImpl#detectLostPartitions can't detect lost partitions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8968) Failed to shutdown node due to "Error saving backup value"
Pavel Vinokurov created IGNITE-8968: --- Summary: Failed to shutdown node due to "Error saving backup value" Key: IGNITE-8968 URL: https://issues.apache.org/jira/browse/IGNITE-8968 Project: Ignite Issue Type: Bug Components: cache, persistence Reporter: Pavel Vinokurov Assignee: Pavel Vinokurov org.apache.ignite.internal.NodeStoppingException: Operation has been cancelled (node is stopping). at org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1263) at org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:370) at org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3626) at org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:2783) at org.apache.ignite.internal.processors.cache.GridCacheUtils$22.process(GridCacheUtils.java:1734) at org.apache.ignite.internal.processors.cache.GridCacheUtils$22.apply(GridCacheUtils.java:1782) at org.apache.ignite.internal.processors.cache.GridCacheUtils$22.apply(GridCacheUtils.java:1724) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8912) PartitionLossPolicy.READ_ONLY_SAFE does not detect partition loss
Pavel Vinokurov created IGNITE-8912: --- Summary: PartitionLossPolicy.READ_ONLY_SAFE does not detect partition loss Key: IGNITE-8912 URL: https://issues.apache.org/jira/browse/IGNITE-8912 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.5 Reporter: Pavel Vinokurov Attachments: MissedPartitionLostReproducer.java Cluster of 4 for a cache with 1 backup and READ_ONLY_SAFE . After forcefully killed two nodes, a partition lost without including in partitionsLost collection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8838) Query cursor is open after INSERT call
Pavel Vinokurov created IGNITE-8838: --- Summary: Query cursor is open after INSERT call Key: IGNITE-8838 URL: https://issues.apache.org/jira/browse/IGNITE-8838 Project: Ignite Issue Type: Bug Components: odbc, platforms, sql Affects Versions: 2.4 Reporter: Pavel Vinokurov Ignite ODBC driver returns open cursor for an insert command. AddStatusRecord: Adding new record: Query cursor is in open state already., rowNum: 0, columnNum: 0 SQLGetDiagField: SQLGetDiagField called: 1 PutString: value: HY010 SQLGetDiagField: SQLGetDiagField called: 2 SQLGetDiagRec: SQLGetDiagRec called SQLGetDiagRec: SQLGetDiagRec called SQLGetDiagRec: SQLGetDiagRec called SQLParamOptions: SQLParamOptions called SQLBindParameter: SQLBindParameter called: 1, 1, 12 SQLBindParameter: SQLBindParameter called: 2, 1, 12 SQLBindParameter: SQLBindParameter called: 3, 1, 12 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8746) EVT_CACHE_REBALANCE_PART_DATA_LOST event received twice on the coordinator node
Pavel Vinokurov created IGNITE-8746: --- Summary: EVT_CACHE_REBALANCE_PART_DATA_LOST event received twice on the coordinator node Key: IGNITE-8746 URL: https://issues.apache.org/jira/browse/IGNITE-8746 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.4 Reporter: Pavel Vinokurov Attachments: EvtDataLostTwiceOnCoordinatorReprocuder.java After a node left the cluster the coordinator recieves the partition lost event twice. The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8716) SQL query and WITH caluse produces syntax error
Pavel Vinokurov created IGNITE-8716:
---
Summary: SQL query and WITH caluse produces syntax error
Key: IGNITE-8716
URL: https://issues.apache.org/jira/browse/IGNITE-8716
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.5
Reporter: Pavel Vinokurov
Initial script:
CREATE TABLE Person(ID INTEGER PRIMARY KEY, NAME VARCHAR(100));
Query:
WITH usr AS (
SELECT * FROM Person p
)
select u.* from usr as u
Result:
Error: Syntax error in SQL statement "WITH USR AS[*] ( SELECT * FROM PERSON P )
SELECT U.* FROM USR AS U "; expected "., ("; SQL statement: WITH usr AS (
SELECT * FROM Person p ) select u.* from usr as u [42001-195]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8552) Unable to use date as primary key
Pavel Vinokurov created IGNITE-8552: --- Summary: Unable to use date as primary key Key: IGNITE-8552 URL: https://issues.apache.org/jira/browse/IGNITE-8552 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.4 Reporter: Pavel Vinokurov It' is unable to create cache via ddl: create table tab(id date primary key, date_field date); Result: ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to rollback cache start routine. [cacheName=SQL_PUBLIC_T3] class org.apache.ignite.IgniteCheckedException: Failed to find value class in the node classpath (use default marshaller to enable binary objects) : SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409 at org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8357) Recreated atomic sequence produces "Sequence was removed from cache"
Pavel Vinokurov created IGNITE-8357: --- Summary: Recreated atomic sequence produces "Sequence was removed from cache" Key: IGNITE-8357 URL: https://issues.apache.org/jira/browse/IGNITE-8357 Project: Ignite Issue Type: Bug Components: data structures Reporter: Pavel Vinokurov Attachments: RecreatingAtomicSequence.java If a cluster have two or more nodes, recreated atomic sequence produces error on incrementAndGet operation. The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8284) Performance SQL with distinct in subquery
Pavel Vinokurov created IGNITE-8284: --- Summary: Performance SQL with distinct in subquery Key: IGNITE-8284 URL: https://issues.apache.org/jira/browse/IGNITE-8284 Project: Ignite Issue Type: New Feature Reporter: Pavel Vinokurov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8072) SQL query with multiple JOIN and subquery with UNION produces "Column not found" exception
Pavel Vinokurov created IGNITE-8072: --- Summary: SQL query with multiple JOIN and subquery with UNION produces "Column not found" exception Key: IGNITE-8072 URL: https://issues.apache.org/jira/browse/IGNITE-8072 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.4, 2.2, 2.1 Reporter: Pavel Vinokurov Initial script: CREATE TABLE Person(id INTEGER PRIMARY KEY, company_id INTEGER); CREATE TABLE Company(id INTEGER PRIMARY KEY, name VARCHAR); CREATE TABLE Department(id INTEGER PRIMARY KEY, company_id INTEGER); Query: select * from ( select p.id as id, p.company_id as company_id from person p union select p.id as id, p.company_id as company_id from person p ) p left join company c on p.company_id=c.id left join department d on p.company_id=d.id Result: SEVERE: Failed to run map query on local node. class org.apache.ignite.IgniteCheckedException: Failed to parse SQL query: SELECT C__Z3.NAME __C2_0, D__Z4.ID __C2_1, D__Z4.COMPANY_ID __C2_2, C__Z3.ID __C2_3 FROM PUBLIC.COMPANY C__Z3 LEFT OUTER JOIN PUBLIC.DEPARTMENT D__Z4 ON P__Z2.COMPANY_ID = D__Z4.ID ORDER BY 4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8009) SQL local query to a cache with queryParallelism>1 doesn't use index
Pavel Vinokurov created IGNITE-8009: --- Summary: SQL local query to a cache with queryParallelism>1 doesn't use index Key: IGNITE-8009 URL: https://issues.apache.org/jira/browse/IGNITE-8009 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.4, 2.3 Reporter: Pavel Vinokurov Attachments: ExplainAndIndexReproducer.java queryParallelism>1 + setLocal(true) changes the query plan and exclude usage of the sql index. Explain query with setLocal(false) and queryParallelism=1 SELECT T__Z0.ID AS __C0_0 FROM TABLE(COL VARCHAR='name0') I__Z1 /* function */ INNER JOIN PUBLIC.PERSON T__Z0 /* PUBLIC.PERSON_NAME: NAME = I__Z1.COL */ ON 1=1 WHERE (T__Z0.SOURNAME = 'sourname0') AND (T__Z0.NAME = I__Z1.COL) Explain query with setLocal(true) and queryParallelism=2 SELECT T__Z1.ID AS __C0_0 FROM PUBLIC.PERSON T__Z1 /* PUBLIC.PERSON.__SCAN_ */ /* WHERE T__Z1.SOURNAME = 'sourname0' */ INNER JOIN TABLE(COL VARCHAR='name0') I__Z0 /* function: COL = T__Z1.NAME */ ON 1=1 WHERE (T__Z1.SOURNAME = 'sourname0') AND (T__Z1.NAME = I__Z0.COL) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7982) IgniteRepositoryFactory are unable to instantiate non-lazy repository
Pavel Vinokurov created IGNITE-7982: --- Summary: IgniteRepositoryFactory are unable to instantiate non-lazy repository Key: IGNITE-7982 URL: https://issues.apache.org/jira/browse/IGNITE-7982 Project: Ignite Issue Type: Bug Components: spring Affects Versions: 2.4 Reporter: Pavel Vinokurov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7968) IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed to acquire lock for keys
Pavel Vinokurov created IGNITE-7968: --- Summary: IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed to acquire lock for keys Key: IGNITE-7968 URL: https://issues.apache.org/jira/browse/IGNITE-7968 Project: Ignite Issue Type: Bug Components: data structures Affects Versions: 2.4, 2.3 Reporter: Pavel Vinokurov Attachments: AtomicSeqAndClusterTopologyReproducer.java When a primary node for a atomic sequnce has left cluster, IgniteAtomicSequence.incrementAndGet could throw ClusterTopologyException. The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7959) Deadlock at GridDhtAtomicCache.lockEntries during parallel SQL delete
Pavel Vinokurov created IGNITE-7959: --- Summary: Deadlock at GridDhtAtomicCache.lockEntries during parallel SQL delete Key: IGNITE-7959 URL: https://issues.apache.org/jira/browse/IGNITE-7959 Project: Ignite Issue Type: Bug Components: cache, sql Affects Versions: 2.3 Reporter: Pavel Vinokurov Attachments: DeadlockOnDelete.java Reproduce steps: 1. Run insert operations from single thread. 2. Run "delete from table limit 50" in 5 threads. The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7879) SQL query with group by and distinct in subquery produces JdbcSQLException
Pavel Vinokurov created IGNITE-7879: --- Summary: SQL query with group by and distinct in subquery produces JdbcSQLException Key: IGNITE-7879 URL: https://issues.apache.org/jira/browse/IGNITE-7879 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.3, 2.1 Reporter: Pavel Vinokurov SQL initial script: CREATE TABLE Person(id INTEGER PRIMARY KEY, company_id INTEGER); CREATE TABLE Company(id INTEGER PRIMARY KEY, name VARCHAR); INSERT INTO Person(id,company_id) VALUES (1, 1), (2, 2), (3, 3); INSERT INTO Company(id,name) VALUES (1,'n1'), (2,'n2'), (3,'n3'); SQL query: SELECT p.id,sum(p.id) FROM person p LEFT JOIN (select DISTINCT id from company) as c on c.id=p.company_id group by p.id Result: Caused by: org.h2.jdbc.JdbcSQLException: Column "P__Z0.ID" must be in the GROUP BY list; SQL statement: SELECT P__Z0.ID __C0_0, P__Z0.COMPANY_ID __C0_1, SUM(P__Z0.ID) __C0_2 FROM PUBLIC.PERSON P__Z0 [90016-195] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7785) SQL query with COUNT and UNION in sub-query produces JdbcSQLException
Pavel Vinokurov created IGNITE-7785: --- Summary: SQL query with COUNT and UNION in sub-query produces JdbcSQLException Key: IGNITE-7785 URL: https://issues.apache.org/jira/browse/IGNITE-7785 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.3, 2.1 Reporter: Pavel Vinokurov SQL initial script: CREATE TABLE Person(id INTEGER PRIMARY KEY, company_id INTEGER); CREATE TABLE Company(id INTEGER PRIMARY KEY, name VARCHAR); INSERT INTO Person(id,company_id) VALUES (1, 1), (2, 2), (3, 3); INSERT INTO Company(id,name) VALUES (1,'n1'), (2,'n2'), (3,'n3'); SQL Query: SELECT count(*) FROM person p LEFT JOIN (select id from company union select id from company) as c on c.id=p.company_id SQL error: Caused by: org.h2.jdbc.JdbcSQLException: Column "P__Z0.COMPANY_ID" must be in the GROUP BY list; SQL statement: SELECT P__Z0.COMPANY_ID __C0_0, COUNT(*) __C0_1 FROM PUBLIC.PERSON P__Z0 [90016-195] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7780) Fix ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon
Pavel Vinokurov created IGNITE-7780: --- Summary: Fix ClientConnectorConfigurationValidationSelfTest#testJdbcConnectionDisabledForDaemon Key: IGNITE-7780 URL: https://issues.apache.org/jira/browse/IGNITE-7780 Project: Ignite Issue Type: Test Reporter: Pavel Vinokurov Assignee: Pavel Vinokurov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7761) EXPLAIN with run time statistics
Pavel Vinokurov created IGNITE-7761: --- Summary: EXPLAIN with run time statistics Key: IGNITE-7761 URL: https://issues.apache.org/jira/browse/IGNITE-7761 Project: Ignite Issue Type: New Feature Components: sql Affects Versions: 2.3 Reporter: Pavel Vinokurov For performance tuning of the sql queries It is nice to have actual run time statistics of the query execution. Statistics could include elapsed time and the number of rows for each query node. Example: ||Rows||Actual Time||Plan Node|| || |1|5ms|group by city|Index scan using person.city| |20|30ms|person.age=5|Full scan(person.age)| |131231|50ms|person.name='John'|Index scan using person_name_idx| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7718) Collections.singleton() and Collections.singletonMap() are not properly serialized by binary marshaller
Pavel Vinokurov created IGNITE-7718: --- Summary: Collections.singleton() and Collections.singletonMap() are not properly serialized by binary marshaller Key: IGNITE-7718 URL: https://issues.apache.org/jira/browse/IGNITE-7718 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.3 Reporter: Pavel Vinokurov Assignee: Pavel Vinokurov After desialization collections obtained by Collections.singleton() and Collections.singletonMap() does not return collection of binary objects, but rather collection of deserialized objects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
