[jira] [Updated] (IGNITE-12089) JVM is halted after this error during rolling restart of a cluster
[ https://issues.apache.org/jira/browse/IGNITE-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] temp2 updated IGNITE-12089: --- Attachment: test2.txt test1.txt > JVM is halted after this error during rolling restart of a cluster > -- > > Key: IGNITE-12089 > URL: https://issues.apache.org/jira/browse/IGNITE-12089 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: temp2 >Priority: Critical > Attachments: IgniteTest2.java, Screenshot_20190909_204710.png, > Screenshot_20190909_204808.png, Screenshot_20190909_204837.png, > default-config.xml, ignite27.log, ignite42.log, test1.txt, test2.txt, > test_test2.java > > > JVM is halted after this error during rolling restart of a cluster: > excepition is :528-a852-c65782e337f0][2019-08-20 > 17:22:10,901][ERROR][ttl-cleanup-worker-#155][] Critical system error > detected. Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailure528-a852-c65782e337f0][2019-08-20 > 17:22:10,901][ERROR][ttl-cleanup-worker-#155][] Critical system error > detected. Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext > [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Runtime > failure on bounds: [lower=PendingRow [], upper=PendingRow > [org.apache.ignite.IgniteException: Runtime failure on bounds: > [lower=PendingRow [], upper=PendingRow []] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:971) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:950) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1022) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:197) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:137) > [ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) > [ignite-core-2.6.0.jar:2.6.0] at java.lang.Thread.run(Thread.java:745) > [?:1.8.0_101]Caused by: 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:83) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:95) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:148) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:102) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingRow.initKey(PendingRow.java:72) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.getRow(PendingEntriesTree.java:118) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.getRow(PendingEntriesTree.java:31) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.fillFromBuffer(BPlusTree.java:4660) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.init(BPlusTree.java:4562) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.access$5300(BPlusTree.java:4501) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetCursor.notFound(BPlusTree.java:2633) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:293) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4816) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4801) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:158) > ~[ignite-core-2.6.0.jar:2.6.0] at >
[jira] [Commented] (IGNITE-12089) JVM is halted after this error during rolling restart of a cluster
[ https://issues.apache.org/jira/browse/IGNITE-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926253#comment-16926253 ] temp2 commented on IGNITE-12089: I can reproduce, see new log attach. [^test1.txt] [^test2.txt] Change the cache expiration time from 15 to 3 minutes to speed up testing， from "createCache(name, TimeUnit.MINUTES, 15, EXPIRY_CREATE, null, STORE_NAME, 1);" to "createCache(name, TimeUnit.MINUTES, 3, EXPIRY_CREATE, null, STORE_NAME, 1);" in testWriteCach and testRemoveCach method. > JVM is halted after this error during rolling restart of a cluster > -- > > Key: IGNITE-12089 > URL: https://issues.apache.org/jira/browse/IGNITE-12089 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: temp2 >Priority: Critical > Attachments: IgniteTest2.java, Screenshot_20190909_204710.png, > Screenshot_20190909_204808.png, Screenshot_20190909_204837.png, > default-config.xml, ignite27.log, ignite42.log, test1.txt, test2.txt, > test_test2.java > > > JVM is halted after this error during rolling restart of a cluster: > excepition is :528-a852-c65782e337f0][2019-08-20 > 17:22:10,901][ERROR][ttl-cleanup-worker-#155][] Critical system error > detected. Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailure528-a852-c65782e337f0][2019-08-20 > 17:22:10,901][ERROR][ttl-cleanup-worker-#155][] Critical system error > detected. Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext > [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Runtime > failure on bounds: [lower=PendingRow [], upper=PendingRow > [org.apache.ignite.IgniteException: Runtime failure on bounds: > [lower=PendingRow [], upper=PendingRow []] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:971) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:950) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1022) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:197) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:137) > [ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) > [ignite-core-2.6.0.jar:2.6.0] at java.lang.Thread.run(Thread.java:745) > [?:1.8.0_101]Caused by: 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:83) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:95) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:148) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:102) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingRow.initKey(PendingRow.java:72) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.getRow(PendingEntriesTree.java:118) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.getRow(PendingEntriesTree.java:31) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.fillFromBuffer(BPlusTree.java:4660) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.init(BPlusTree.java:4562) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.access$5300(BPlusTree.java:4501) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetCursor.notFound(BPlusTree.java:2633) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:293) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4816) > ~[ignite-core-2.6.0.jar:2.6.0] at >
[jira] [Commented] (IGNITE-11905) [IEP-35] Monitoring Phase 2
[ https://issues.apache.org/jira/browse/IGNITE-11905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926087#comment-16926087 ] Vyacheslav Daradur commented on IGNITE-11905: - [~NIzhikov], thank you for the patch, great work! I left some minor pr comments on GitHub. > [IEP-35] Monitoring Phase 2 > -- > > Key: IGNITE-11905 > URL: https://issues.apache.org/jira/browse/IGNITE-11905 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > > Phase 2 should introduce: > Ability to collect lists of some internal object Ignite manage. > Examples of such objects: > * Caches > * Queries (including continuous queries) > * Services > * Compute tasks > * Distributed Data Structures > * etc... > 1. Fields for each list should be discussed in separate tickets > 2. Metric Exporters (optionally) can support list export. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12012) .NET: ICompute.WithExecutor
[ https://issues.apache.org/jira/browse/IGNITE-12012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-12012: Labels: .NET (was: ) > .NET: ICompute.WithExecutor > --- > > Key: IGNITE-12012 > URL: https://issues.apache.org/jira/browse/IGNITE-12012 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > > Propagate the following APIs to .NET: > * IgniteCompute.withExecutor > * IgniteConfiguration.ExecutorConfiguration -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (IGNITE-12012) .NET: ICompute.WithExecutor
[ https://issues.apache.org/jira/browse/IGNITE-12012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-12012. - Fix Version/s: 2.8 Reviewer: Alexandr Shapkin Resolution: Done > .NET: ICompute.WithExecutor > --- > > Key: IGNITE-12012 > URL: https://issues.apache.org/jira/browse/IGNITE-12012 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.8 > > > Propagate the following APIs to .NET: > * IgniteCompute.withExecutor > * IgniteConfiguration.ExecutorConfiguration -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12012) .NET: ICompute.WithExecutor
[ https://issues.apache.org/jira/browse/IGNITE-12012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926058#comment-16926058 ] Pavel Tupitsyn commented on IGNITE-12012: - Merged to master: 5215e67403f1bd7c49e6a609adc200a89c39cbf9 > .NET: ICompute.WithExecutor > --- > > Key: IGNITE-12012 > URL: https://issues.apache.org/jira/browse/IGNITE-12012 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > > Propagate the following APIs to .NET: > * IgniteCompute.withExecutor > * IgniteConfiguration.ExecutorConfiguration -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12032) Server node prints exception when ODBC driver disconnects
[
https://issues.apache.org/jira/browse/IGNITE-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925966#comment-16925966
]
Lev Agafonov commented on IGNITE-12032:
---
Hello!
I'd like to work on this ticket. Could you please assign it to me?
> Server node prints exception when ODBC driver disconnects
> -
>
> Key: IGNITE-12032
> URL: https://issues.apache.org/jira/browse/IGNITE-12032
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.7.5
>Reporter: Evgenii Zhuravlev
>Priority: Major
> Labels: newbie, usability
> Fix For: 2.8
>
>
> Whenever a process using ODBC clients is finished, it's printing in the
> node logs this exception:
> {code:java}
> *[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
>
> Failed to process selector key [s
> es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker
> [readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192
> ], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0,
> bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo
> rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null,
> finished=false, heartbeatTs=1564289118230, hashCo
> de=1829856117, interrupted=false,
> runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null,
> readBuf=null, inRecove
> ry=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre
> ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588,
> bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623
> 5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioAsyn
> cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser,
> directMode=false]], accepted=true, markedForClos
> e=false]]]
> java.io.IOException: An existing connection was forcibly closed by the
> remote host
> at sun.nio.ch.SocketDispatcher.read0(Native Method)
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
>
> 04)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
>
> oServer.java:2389)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
>
> 6)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
>
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)*
> {code}
> It's absolutely normal behavior when ODBC client disconnects from the node,
> so, we shouldn't print exception in the log. We should replace it with
> something like INFO message about ODBC client disconnection.
> Thread from user list:
> http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12089) JVM is halted after this error during rolling restart of a cluster
[ https://issues.apache.org/jira/browse/IGNITE-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925959#comment-16925959 ] Stanilovsky Evgeny commented on IGNITE-12089: - i check your scenario and still can`t reproduce, check attach. > JVM is halted after this error during rolling restart of a cluster > -- > > Key: IGNITE-12089 > URL: https://issues.apache.org/jira/browse/IGNITE-12089 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: temp2 >Priority: Critical > Attachments: IgniteTest2.java, Screenshot_20190909_204710.png, > Screenshot_20190909_204808.png, Screenshot_20190909_204837.png, > default-config.xml, ignite27.log, ignite42.log, test_test2.java > > > JVM is halted after this error during rolling restart of a cluster: > excepition is :528-a852-c65782e337f0][2019-08-20 > 17:22:10,901][ERROR][ttl-cleanup-worker-#155][] Critical system error > detected. Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailure528-a852-c65782e337f0][2019-08-20 > 17:22:10,901][ERROR][ttl-cleanup-worker-#155][] Critical system error > detected. Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext > [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Runtime > failure on bounds: [lower=PendingRow [], upper=PendingRow > [org.apache.ignite.IgniteException: Runtime failure on bounds: > [lower=PendingRow [], upper=PendingRow []] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:971) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:950) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1022) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:197) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:137) > [ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) > [ignite-core-2.6.0.jar:2.6.0] at java.lang.Thread.run(Thread.java:745) > [?:1.8.0_101]Caused by: 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:83) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:95) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:148) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:102) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingRow.initKey(PendingRow.java:72) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.getRow(PendingEntriesTree.java:118) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.getRow(PendingEntriesTree.java:31) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.fillFromBuffer(BPlusTree.java:4660) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.init(BPlusTree.java:4562) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.access$5300(BPlusTree.java:4501) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetCursor.notFound(BPlusTree.java:2633) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:293) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4816) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4801) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(PageHandler.java:158) >
[jira] [Updated] (IGNITE-12089) JVM is halted after this error during rolling restart of a cluster
[ https://issues.apache.org/jira/browse/IGNITE-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-12089: Attachment: Screenshot_20190909_204837.png Screenshot_20190909_204808.png Screenshot_20190909_204710.png > JVM is halted after this error during rolling restart of a cluster > -- > > Key: IGNITE-12089 > URL: https://issues.apache.org/jira/browse/IGNITE-12089 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: temp2 >Priority: Critical > Attachments: IgniteTest2.java, Screenshot_20190909_204710.png, > Screenshot_20190909_204808.png, Screenshot_20190909_204837.png, > default-config.xml, ignite27.log, ignite42.log, test_test2.java > > > JVM is halted after this error during rolling restart of a cluster: > excepition is :528-a852-c65782e337f0][2019-08-20 > 17:22:10,901][ERROR][ttl-cleanup-worker-#155][] Critical system error > detected. Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailure528-a852-c65782e337f0][2019-08-20 > 17:22:10,901][ERROR][ttl-cleanup-worker-#155][] Critical system error > detected. Will be handled accordingly to configured handler [hnd=class > o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext > [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Runtime > failure on bounds: [lower=PendingRow [], upper=PendingRow > [org.apache.ignite.IgniteException: Runtime failure on bounds: > [lower=PendingRow [], upper=PendingRow []] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:971) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:950) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1022) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:197) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:137) > [ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) > [ignite-core-2.6.0.jar:2.6.0] at java.lang.Thread.run(Thread.java:745) > [?:1.8.0_101]Caused by: 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:83) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:95) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:148) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:102) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingRow.initKey(PendingRow.java:72) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.getRow(PendingEntriesTree.java:118) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.getRow(PendingEntriesTree.java:31) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.fillFromBuffer(BPlusTree.java:4660) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.init(BPlusTree.java:4562) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.access$5300(BPlusTree.java:4501) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetCursor.notFound(BPlusTree.java:2633) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(BPlusTree.java:293) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4816) > ~[ignite-core-2.6.0.jar:2.6.0] at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:4801) > ~[ignite-core-2.6.0.jar:2.6.0] at >
[jira] [Commented] (IGNITE-12151) Load Cache: Failed to load bean in app context
[ https://issues.apache.org/jira/browse/IGNITE-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925867#comment-16925867 ] Kurt Semba commented on IGNITE-12151: - Hi all, it seems that this was a misunderstanding on the overall workflow on my side. I got ignite to import data from my MySQL DB by running the cluster out of my IDE with the pre-built DB schema (using file ServerNodeSpringStartup.java). When run LoadCaches.java afterwards, it works fine. So in order to get my scenario to work I will have to provide the XML config file for my cluster in advance (at the point of startup). My impression was that I could create cache defintions on a running ignite cluster on the fly. But it seems that the cluster needs to be aware of all DB schemas it should talk to at the moment of startup. Thanks Kurt > Load Cache: Failed to load bean in app context > -- > > Key: IGNITE-12151 > URL: https://issues.apache.org/jira/browse/IGNITE-12151 > Project: Ignite > Issue Type: Bug > Components: binary, cache >Affects Versions: 2.7.5 > Environment: * Ubuntu 18.04 > * Ignite server v2.7.5 - running in a docker container with the REST API > module enabled > * Ignite web-console: 2.7.0 - also running in a docker container > * Ignite web-agent - downloaded from the web-console so I assume also using > version 2.7.0 - not running in a docker container (properly connects to both > the web-console as well as the cluster... until I kill my cluster ;) ) > * MySQL DB: v5.7 running on a remote VM > * IDE: Visual Studio Code (latest update) >Reporter: Kurt Semba >Priority: Major > Attachments: Dockerfile, clientLoadCaches.log, cluster.log > > > Hi team, > I was following the instructions from > [https://www.youtube.com/watch?v=SJ6h55VhUBI] and onwards to use the > web-console and web-agent to import data from a MySQL DB. It all works fine > until I download the cluster configuration Java project from the web-console > and try to run the "LoadCaches" java file in my IDE. > The client (LoadCaches code) fails with an "IgniteCheckedException: Failed to > connect to node" exception but more importantly, the ignite cluster crashes > as well with an "IgniteException: Failed to load bean in application context" > exception. See both logs attached. > The parts where I diverged from the demo video series: > * I did not tweak the cluster config using the web-console - just kept it as > it was auto-created by the web-console > * I edited /src/main/resources/META-INF/ImportedCluster-client.xml and > configured the IP of my Ignite cluster (both the ignite cluster and the IDE > code are running on the same server, but using the default 127.0.0.1 didn't > connect) > * I edited the pom.xml file to make the Java code use the latest v2.7.5 > libraries to load the cache (since the cluster is also running this version) > > Do I have to somehow pre-stage the cluster / cache with the DB table I'm > trying to import? I was hoping that the web-console would do that when I use > the "Import from Database" wizard? > Maybe the version mismatch between web-console (2.7.0) and cluster (2.7.5) is > an issue? > Thanks > Kurt -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12128) Potentially pds corruption on a failed node during checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-12128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-12128: -- Release Note: Fixed an issue causing potential PDS corruption when a node is killed during checkpoint mark phase > Potentially pds corruption on a failed node during checkpoint > - > > Key: IGNITE-12128 > URL: https://issues.apache.org/jira/browse/IGNITE-12128 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Anton Kalashnikov >Priority: Critical > Fix For: 2.7.6 > > Time Spent: 20m > Remaining Estimate: 0h > > There are the case when we start a checkpoint but not create CP file marker, > but PageMemory may start to flush dirty pages from checkpoint pages to page > store. If node crashed at this moment, we can get inconsistency state, > because we still not write checkpoint marker to disk but already write some > pages for this checkpoint. If we try to recover from this state we cat get > any sort of corruption problem. Recovery logic may not recognize that crash > was during checkpoint because we did not write file marker when we start > checkpoint but write some pages for this checkpoint. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12150) Ignite javadoc contains bogus links, copyright is outdated
[
https://issues.apache.org/jira/browse/IGNITE-12150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12150:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> Ignite javadoc contains bogus links, copyright is outdated
> --
>
> Key: IGNITE-12150
> URL: https://issues.apache.org/jira/browse/IGNITE-12150
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.7.6
>
>
> Ignite Javadoc contains links to {{http://agorbatchev.typepad.com}} which may
> be broken and unnecessary. Also, the copyright year is hardcoded and outdated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (IGNITE-12150) Ignite javadoc contains bogus links, copyright is outdated
[
https://issues.apache.org/jira/browse/IGNITE-12150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk resolved IGNITE-12150.
---
Resolution: Fixed
Visa is not required since changes are validated manually. Merged to master and
ignite-2.7.6
> Ignite javadoc contains bogus links, copyright is outdated
> --
>
> Key: IGNITE-12150
> URL: https://issues.apache.org/jira/browse/IGNITE-12150
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.7.6
>
>
> Ignite Javadoc contains links to {{http://agorbatchev.typepad.com}} which may
> be broken and unnecessary. Also, the copyright year is hardcoded and outdated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (IGNITE-12106) Rework ignite binary metadata exception for ease of troubleshooting
[
https://issues.apache.org/jira/browse/IGNITE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12106:
--
Fix Version/s: (was: 2.7.6)
2.8
> Rework ignite binary metadata exception for ease of troubleshooting
> ---
>
> Key: IGNITE-12106
> URL: https://issues.apache.org/jira/browse/IGNITE-12106
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence
>Affects Versions: 2.7.5, 2.7.6
>Reporter: Denis Magda
>Priority: Blocker
> Fix For: 2.8
>
>
> An exception of this kind happens regularly and its message doesn't suggest
> why it took place and how to fix the issue:
> {noformat}
> Cannot find metadata for object with compact footer: 2097659979
> {noformat}
> See this thread for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html
> As a solution, let's rework this exception to ensure that the way like that
> "Ignite work directory might be cleared on restarts. Ensure that IGNITE_HOME
> doesn't point to a temp folder or any other folder that is destroyed/erased
> on restarts. Presently, IGNITE_HOME points to..."
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (IGNITE-12106) Rework ignite binary metadata exception for ease of troubleshooting
[
https://issues.apache.org/jira/browse/IGNITE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-12106:
--
Fix Version/s: (was: 2.8)
2.7.6
> Rework ignite binary metadata exception for ease of troubleshooting
> ---
>
> Key: IGNITE-12106
> URL: https://issues.apache.org/jira/browse/IGNITE-12106
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence
>Affects Versions: 2.7.5, 2.7.6
>Reporter: Denis Magda
>Priority: Blocker
> Fix For: 2.7.6
>
>
> An exception of this kind happens regularly and its message doesn't suggest
> why it took place and how to fix the issue:
> {noformat}
> Cannot find metadata for object with compact footer: 2097659979
> {noformat}
> See this thread for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html
> As a solution, let's rework this exception to ensure that the way like that
> "Ignite work directory might be cleared on restarts. Ensure that IGNITE_HOME
> doesn't point to a temp folder or any other folder that is destroyed/erased
> on restarts. Presently, IGNITE_HOME points to..."
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (IGNITE-12153) Control.sh add test for checking that help and cache help output are not broken.
[ https://issues.apache.org/jira/browse/IGNITE-12153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-12153: Labels: MakeTeamcityGreenAgain (was: ) > Control.sh add test for checking that help and cache help output are not > broken. > > > Key: IGNITE-12153 > URL: https://issues.apache.org/jira/browse/IGNITE-12153 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > We should store "ideal" outputs in resorces and compare with current. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12153) Control.sh add test for checking that help and cache help output are not broken.
[ https://issues.apache.org/jira/browse/IGNITE-12153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-12153: Ignite Flags: (was: Release Notes Required) > Control.sh add test for checking that help and cache help output are not > broken. > > > Key: IGNITE-12153 > URL: https://issues.apache.org/jira/browse/IGNITE-12153 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > > We should store "ideal" outputs in resorces and compare with current. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-12153) Control.sh add test for checking that help and cache help output are not broken.
[ https://issues.apache.org/jira/browse/IGNITE-12153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-12153: Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Control.sh add test for checking that help and cache help output are not > broken. > > > Key: IGNITE-12153 > URL: https://issues.apache.org/jira/browse/IGNITE-12153 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > > We should store "ideal" outputs in resorces and compare with current. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12153) Control.sh add test for checking that help and cache help output are not broken.
Sergey Antonov created IGNITE-12153: --- Summary: Control.sh add test for checking that help and cache help output are not broken. Key: IGNITE-12153 URL: https://issues.apache.org/jira/browse/IGNITE-12153 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 We should store "ideal" outputs in resorces and compare with current. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (IGNITE-12128) Potentially pds corruption on a failed node during checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-12128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925701#comment-16925701 ] Alexey Goncharuk edited comment on IGNITE-12128 at 9/9/19 1:41 PM: --- [~akalashnikov] thanks, merged your changes to master and ignite-2.7.6! was (Author: agoncharuk): [~akalashnikov] thanks, merged your changes to master! > Potentially pds corruption on a failed node during checkpoint > - > > Key: IGNITE-12128 > URL: https://issues.apache.org/jira/browse/IGNITE-12128 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Anton Kalashnikov >Priority: Critical > Fix For: 2.7.6 > > Time Spent: 20m > Remaining Estimate: 0h > > There are the case when we start a checkpoint but not create CP file marker, > but PageMemory may start to flush dirty pages from checkpoint pages to page > store. If node crashed at this moment, we can get inconsistency state, > because we still not write checkpoint marker to disk but already write some > pages for this checkpoint. If we try to recover from this state we cat get > any sort of corruption problem. Recovery logic may not recognize that crash > was during checkpoint because we did not write file marker when we start > checkpoint but write some pages for this checkpoint. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12128) Potentially pds corruption on a failed node during checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-12128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925701#comment-16925701 ] Alexey Goncharuk commented on IGNITE-12128: --- [~akalashnikov] thanks, merged your changes to master! > Potentially pds corruption on a failed node during checkpoint > - > > Key: IGNITE-12128 > URL: https://issues.apache.org/jira/browse/IGNITE-12128 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Anton Kalashnikov >Priority: Critical > Fix For: 2.7.6 > > Time Spent: 20m > Remaining Estimate: 0h > > There are the case when we start a checkpoint but not create CP file marker, > but PageMemory may start to flush dirty pages from checkpoint pages to page > store. If node crashed at this moment, we can get inconsistency state, > because we still not write checkpoint marker to disk but already write some > pages for this checkpoint. If we try to recover from this state we cat get > any sort of corruption problem. Recovery logic may not recognize that crash > was during checkpoint because we did not write file marker when we start > checkpoint but write some pages for this checkpoint. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-12123) Cache throws npe at {null, null, null} array key.
[
https://issues.apache.org/jira/browse/IGNITE-12123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925689#comment-16925689
]
Stepachev Maksim commented on IGNITE-12123:
---
[~Jokser] please make the review.
> Cache throws npe at {null, null, null} array key.
> -
>
> Key: IGNITE-12123
> URL: https://issues.apache.org/jira/browse/IGNITE-12123
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When we put null-key to ignite cache we get NPE with the problem description
> "java.lang.NullPointerException: Ouch! Argument cannot be null: key"
> But when we put "new String[]
> {"c", *null*, "a"}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12123) Cache throws npe at {null, null, null} array key.
[
https://issues.apache.org/jira/browse/IGNITE-12123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925685#comment-16925685
]
Stepachev Maksim commented on IGNITE-12123:
---
[~xtern] please look at this.
> Cache throws npe at {null, null, null} array key.
> -
>
> Key: IGNITE-12123
> URL: https://issues.apache.org/jira/browse/IGNITE-12123
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When we put null-key to ignite cache we get NPE with the problem description
> "java.lang.NullPointerException: Ouch! Argument cannot be null: key"
> But when we put "new String[]
> {"c", *null*, "a"}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12123) Cache throws npe at {null, null, null} array key.
[
https://issues.apache.org/jira/browse/IGNITE-12123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925682#comment-16925682
]
Ignite TC Bot commented on IGNITE-12123:
{panel:title=Branch: [pull/6828/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4552044buildTypeId=IgniteTests24Java8_RunAll]
> Cache throws npe at {null, null, null} array key.
> -
>
> Key: IGNITE-12123
> URL: https://issues.apache.org/jira/browse/IGNITE-12123
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When we put null-key to ignite cache we get NPE with the problem description
> "java.lang.NullPointerException: Ouch! Argument cannot be null: key"
> But when we put "new String[]
> {"c", *null*, "a"}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (IGNITE-2636) Server cache metrics for put-get-remove avg time are incorrect for case when request sent from client
[ https://issues.apache.org/jira/browse/IGNITE-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-2636. - Resolution: Duplicate > Server cache metrics for put-get-remove avg time are incorrect for case when > request sent from client > - > > Key: IGNITE-2636 > URL: https://issues.apache.org/jira/browse/IGNITE-2636 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Vladimir Ershov >Priority: Major > Original Estimate: 120h > Remaining Estimate: 120h > > Server cache metrics for put-get-remove avg time are incorrect for case when > request sent from client. > We should add methods like CacheMetrics#addPutAndGetTimeNanos for all flows, > when requests for cache modifications are processed. For all type of caches. > This will fix CacheMetricsForClusterGroupSelfTest -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (IGNITE-7285) Add default query timeout
[
https://issues.apache.org/jira/browse/IGNITE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925649#comment-16925649
]
Ivan Pavlukhin edited comment on IGNITE-7285 at 9/9/19 12:42 PM:
-
[~samaitra], sorry for a late response. I left a couple of comments on GitHub.
Regarding _unset_ timeout. I think that it would be more straightforward to
have a following logic:
* Unset timeout means that a default one should be used.
* Explicitly set timeout must be used.
* Timeout values have the same meaning for {{SqlFieldsQuery.setTimeout}} and
{{IgniteConfiguration.setDefaultQueryTimeout}}. Consequently 0 means infinite
timeout for both methods.
Technically it can be done in a following way:
# {{SqlFieldsQuery}} declares {{private int timeout = -1}}.
# {{SqlFieldsQuery.setTimeout}} forbids negative arguments.
# Upon {{QueryParameters}} initialization we treat -1 as _unset_ value and use
a default one.
A care should be taken when we create {{SqlFieldsQuery}} internally for an
execution, like in {{OdbcRequestHandler}}.
was (Author: pavlukhin):
[~samaitra], I left a couple of comments on GitHub.
Regarding _unset_ timeout. I think that it would be more straightforward to
have a following logic:
* Unset timeout means that a default one should be used.
* Explicitly set timeout must be used.
* Timeout values have the same meaning for {{SqlFieldsQuery.setTimeout}} and
{{IgniteConfiguration.setDefaultQueryTimeout}}. Consequently 0 means infinite
timeout for both methods.
Technically it can be done in a following way:
# {{SqlFieldsQuery}} declares {{private int timeout = -1}}.
# {{SqlFieldsQuery.setTimeout}} forbids negative arguments.
# Upon {{QueryParameters}} initialization we treat -1 as _unset_ value and use
a default one.
A care should be taken when we create {{SqlFieldsQuery}} internally for an
execution, like in {{OdbcRequestHandler}}.
> Add default query timeout
> -
>
> Key: IGNITE-7285
> URL: https://issues.apache.org/jira/browse/IGNITE-7285
> Project: Ignite
> Issue Type: Improvement
> Components: cache, sql
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Saikat Maitra
>Priority: Major
> Labels: sql-stability
> Fix For: 2.8
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Currently it's possible to provide timeout only on query level. It would be
> very useful to have default timeout value provided on cache startup. Let's
> add {{CacheConfiguration#defaultQueryTimeout}} configuration property.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-7285) Add default query timeout
[
https://issues.apache.org/jira/browse/IGNITE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925649#comment-16925649
]
Ivan Pavlukhin commented on IGNITE-7285:
[~samaitra], I left a couple of comments on GitHub.
Regarding _unset_ timeout. I think that it would be more straightforward to
have a following logic:
* Unset timeout means that a default one should be used.
* Explicitly set timeout must be used.
* Timeout values have the same meaning for {{SqlFieldsQuery.setTimeout}} and
{{IgniteConfiguration.setDefaultQueryTimeout}}. Consequently 0 means infinite
timeout for both methods.
Technically it can be done in a following way:
# {{SqlFieldsQuery}} declares {{private int timeout = -1}}.
# {{SqlFieldsQuery.setTimeout}} forbids negative arguments.
# Upon {{QueryParameters}} initialization we treat -1 as _unset_ value and use
a default one.
A care should be taken when we create {{SqlFieldsQuery}} internally for an
execution, like in {{OdbcRequestHandler}}.
> Add default query timeout
> -
>
> Key: IGNITE-7285
> URL: https://issues.apache.org/jira/browse/IGNITE-7285
> Project: Ignite
> Issue Type: Improvement
> Components: cache, sql
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Saikat Maitra
>Priority: Major
> Labels: sql-stability
> Fix For: 2.8
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Currently it's possible to provide timeout only on query level. It would be
> very useful to have default timeout value provided on cache startup. Let's
> add {{CacheConfiguration#defaultQueryTimeout}} configuration property.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-11624) Discovery SPI: The client can handle events from the previous cluster after reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-11624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925643#comment-16925643
]
Aleksey Plekhanov commented on IGNITE-11624:
[~akalashnikov], still waiting for your answer.
Patch looks good to me, your upsource comments are answered. If you are not
interested in this ticket anymore, I will merge ticket in the next couple of
days.
> Discovery SPI: The client can handle events from the previous cluster after
> reconnect.
> --
>
> Key: IGNITE-11624
> URL: https://issues.apache.org/jira/browse/IGNITE-11624
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Discovery has a queue for events. It's processed by event thread. If we hold
> up event processing using a listener on the client side and restarts cluster
> - the client will reconnect. After it reconnects it will continue processing
> events from the previous cluster.
> This behavior produces bugs in MvccProcessor (IGNITE-11460) and [hanging of
> partitions exchange|https://github.com/NSAmelchev/ignite/pull/26/files] on
> the client side. The reason is that discovery notifies components about
> reconnection in the notifier thread by calling the 'onLocalJoin' method.
> After it (or at the same time), components can process events from the
> previous cluster in their listeners and break their logic.
> The order of events is fine - after processing previous cluster events - it
> will process client disconnection/reconnection and new cluster events.
> The possible solution is to fix discovery logic. Make a guarantee that no one
> event from the previous cluster will be processed after the client reconnect
> ('onLocalJoin' called). For example, wait for the client disconnect event
> will be processed in the discovery event thread. Then start attempt to
> reconnect.
> [Dev-list
> discussion.|http://apache-ignite-developers.2346864.n4.nabble.com/The-client-can-handle-events-from-the-previous-cluster-after-reconnect-td41392.html]
> [Reproducer.|https://github.com/NSAmelchev/ignite/pull/26/files]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IGNITE-12152) Disk space not getting released after deleting rows from a table or after records expired with expiration policy
shivakumar created IGNITE-12152: --- Summary: Disk space not getting released after deleting rows from a table or after records expired with expiration policy Key: IGNITE-12152 URL: https://issues.apache.org/jira/browse/IGNITE-12152 Project: Ignite Issue Type: Bug Components: documentation, persistence, sql Affects Versions: 2.7 Reporter: shivakumar To reproduce, create a cache group and create a sql table using that cache group, then insert considerable rows of records to the table, monitor the disk space usage, now stop inserting records and delete records from the table using *DELETE FROM table; (not a drop table operation)* once this is done the *select count(*) from table;* shows the count 0 but after this when disk space is monitored it will be in the same usage level as it is in the level before rows deletion. When I start inserting records again, the new records re-used the space occupied by the deleted records but still, it is not a good idea to unnecessarily hold disk resource. The same can be reproduced by configuring cache expiry policy (CreatedExpiryPolicy) where after records expires it will not be visible in sql query (select * from table) but still it will hold disk resource. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12151) Load Cache: Failed to load bean in app context
Kurt Semba created IGNITE-12151: --- Summary: Load Cache: Failed to load bean in app context Key: IGNITE-12151 URL: https://issues.apache.org/jira/browse/IGNITE-12151 Project: Ignite Issue Type: Bug Components: binary, cache Affects Versions: 2.7.5 Environment: * Ubuntu 18.04 * Ignite server v2.7.5 - running in a docker container with the REST API module enabled * Ignite web-console: 2.7.0 - also running in a docker container * Ignite web-agent - downloaded from the web-console so I assume also using version 2.7.0 - not running in a docker container (properly connects to both the web-console as well as the cluster... until I kill my cluster ;) ) * MySQL DB: v5.7 running on a remote VM * IDE: Visual Studio Code (latest update) Reporter: Kurt Semba Attachments: Dockerfile, clientLoadCaches.log, cluster.log Hi team, I was following the instructions from [https://www.youtube.com/watch?v=SJ6h55VhUBI] and onwards to use the web-console and web-agent to import data from a MySQL DB. It all works fine until I download the cluster configuration Java project from the web-console and try to run the "LoadCaches" java file in my IDE. The client (LoadCaches code) fails with an "IgniteCheckedException: Failed to connect to node" exception but more importantly, the ignite cluster crashes as well with an "IgniteException: Failed to load bean in application context" exception. See both logs attached. The parts where I diverged from the demo video series: * I did not tweak the cluster config using the web-console - just kept it as it was auto-created by the web-console * I edited /src/main/resources/META-INF/ImportedCluster-client.xml and configured the IP of my Ignite cluster (both the ignite cluster and the IDE code are running on the same server, but using the default 127.0.0.1 didn't connect) * I edited the pom.xml file to make the Java code use the latest v2.7.5 libraries to load the cache (since the cluster is also running this version) Do I have to somehow pre-stage the cluster / cache with the DB table I'm trying to import? I was hoping that the web-console would do that when I use the "Import from Database" wizard? Maybe the version mismatch between web-console (2.7.0) and cluster (2.7.5) is an issue? Thanks Kurt -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12150) Ignite javadoc contains bogus links, copyright is outdated
Alexey Goncharuk created IGNITE-12150:
-
Summary: Ignite javadoc contains bogus links, copyright is outdated
Key: IGNITE-12150
URL: https://issues.apache.org/jira/browse/IGNITE-12150
Project: Ignite
Issue Type: Bug
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
Ignite Javadoc contains links to {{http://agorbatchev.typepad.com}} which may
be broken and unnecessary. Also, the copyright year is hardcoded and outdated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12128) Potentially pds corruption on a failed node during checkpoint
[
https://issues.apache.org/jira/browse/IGNITE-12128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925528#comment-16925528
]
Ignite TC Bot commented on IGNITE-12128:
{panel:title=Branch: [pull/6851/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4574261buildTypeId=IgniteTests24Java8_RunAll]
> Potentially pds corruption on a failed node during checkpoint
> -
>
> Key: IGNITE-12128
> URL: https://issues.apache.org/jira/browse/IGNITE-12128
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Anton Kalashnikov
>Priority: Critical
> Fix For: 2.7.6
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are the case when we start a checkpoint but not create CP file marker,
> but PageMemory may start to flush dirty pages from checkpoint pages to page
> store. If node crashed at this moment, we can get inconsistency state,
> because we still not write checkpoint marker to disk but already write some
> pages for this checkpoint. If we try to recover from this state we cat get
> any sort of corruption problem. Recovery logic may not recognize that crash
> was during checkpoint because we did not write file marker when we start
> checkpoint but write some pages for this checkpoint.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12145) [IEP-35] Monitoring list engine
[
https://issues.apache.org/jira/browse/IGNITE-12145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925453#comment-16925453
]
Nikolay Izhikov commented on IGNITE-12145:
--
This PR contains:
* Monitoring list engine.
** Support for SQL, JMX, Log exporters implemented.
** Internal MonitoringList API added.
** Enable/Disable of lists implemented.
* Following list implemented:
** Cache list
** Cache group list
** Compute task list
** Service list.
Engine details:
* {{MonitoringList}} added to store list data.
* Base interface {{MonitoringRow` for list data created.
* Corresponding method added to {{MetricExporterSpi}}
* {{JmxMetricExporterSpi}}, {{SqlViewExporterSpi}}, {{LogExporterSpi}} updated
to support list export.
* JMX, SQL and other column-oriented SPI uses {{MonitoringRowAttributeWalker}}
to quickly traverse all list row attributes.
* Implementation of {{MonitoringRowAttributeWalker}} for specific
{{MonitoringRow}} can be generated with
{{MonitoringRowAttributeWalkerGenerator}}
> [IEP-35] Monitoring list engine
> ---
>
> Key: IGNITE-12145
> URL: https://issues.apache.org/jira/browse/IGNITE-12145
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.7.5
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The base engine for the monitoring list.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (IGNITE-12135) Rework GridCommandHandlerTest
[ https://issues.apache.org/jira/browse/IGNITE-12135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925410#comment-16925410 ] Kirill Tkalenko commented on IGNITE-12135: -- Deleted @Test. > Rework GridCommandHandlerTest > - > > Key: IGNITE-12135 > URL: https://issues.apache.org/jira/browse/IGNITE-12135 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > There are 50+ tests. In each test we are start and stop nodes. I think we > could split tests at least to two groups: > # Tests on normal behaviour. We could start nodes before all tests and stop > them after all tests. > # Tests required start new cluster before each test. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Issue Comment Deleted] (IGNITE-11410) Sandbox for user-defined code
[
https://issues.apache.org/jira/browse/IGNITE-11410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-11410:
--
Comment: was deleted
(was: {panel:title=Branch: [pull/6750/head] Base: [master] : Possible Blockers
(115)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ (Linux)*{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574670]]
{color:#d04437}Cache 6{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574699]]
{color:#d04437}PDS (Indexing){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574709]]
{color:#d04437}Data Structures{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574706]]
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574668]]
{color:#d04437}Scala (Examples){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574666]]
{color:#d04437}MVCC PDS 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574739]]
{color:#d04437}MVCC PDS 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574741]]
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574669]]
{color:#d04437}Platform .NET (Long Running){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574719]]
{color:#d04437}SPI{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574661]]
{color:#d04437}Cache 8{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574701]]
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574698]]
{color:#d04437}Cache 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574696]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574716]]
{color:#d04437}PDS (Compatibility){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574708]]
{color:#d04437}Scala (Visor Console){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574667]]
{color:#d04437}RDD{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574655]]
{color:#d04437}Examples{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574642]]
{color:#d04437}MVCC Cache 7{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574735]]
{color:#d04437}Platform .NET{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574715]]
{color:#d04437}Start Nodes{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574660]]
{color:#d04437}Cache (Expiry Policy){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574684]]
{color:#d04437}PDS 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574712]]
{color:#d04437}Streamers{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574659]]
{color:#d04437}Cache 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574695]]
{color:#d04437}MVCC Cache 8{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574736]]
{color:#d04437}PDS 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574713]]
{color:#d04437}Queries 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574721]]
{color:#d04437}Continuous Query 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574704]]
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574723]]
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574724]]
{color:#d04437}Continuous Query 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574705]]
{color:#d04437}Basic 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574673]]
{color:#d04437}Cache (Restarts) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574691]]
{color:#d04437}Cache 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574694]]
{color:#d04437}MVCC Queries{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574679]]
{color:#d04437}PDS 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574714]]
{color:#d04437}MVCC Cache 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=4574729]]
[jira] [Resolved] (IGNITE-7221) Web console: Fractional value in memory field
[ https://issues.apache.org/jira/browse/IGNITE-7221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-7221. -- Resolution: Cannot Reproduce > Web console: Fractional value in memory field > - > > Key: IGNITE-7221 > URL: https://issues.apache.org/jira/browse/IGNITE-7221 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.1 >Reporter: Vasiliy Sisko >Assignee: Ilya Borisov >Priority: Major > > # Open basic page of configuration. > # Input fractional value into Off-heap size field (f.e. 1000951.4249753) > Value is showed as valid. > On download fractional value is generated instead of long value in bytes > (1024974259.1747072) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (IGNITE-7221) Web console: Fractional value in memory field
[ https://issues.apache.org/jira/browse/IGNITE-7221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-7221. > Web console: Fractional value in memory field > - > > Key: IGNITE-7221 > URL: https://issues.apache.org/jira/browse/IGNITE-7221 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.1 >Reporter: Vasiliy Sisko >Assignee: Ilya Borisov >Priority: Major > > # Open basic page of configuration. > # Input fractional value into Off-heap size field (f.e. 1000951.4249753) > Value is showed as valid. > On download fractional value is generated instead of long value in bytes > (1024974259.1747072) -- This message was sent by Atlassian Jira (v8.3.2#803003)
