[jira] [Created] (IGNITE-14686) Incorrect type hint for the cache's get_all in the Python thin client
Robert Emanuele created IGNITE-14686: Summary: Incorrect type hint for the cache's get_all in the Python thin client Key: IGNITE-14686 URL: https://issues.apache.org/jira/browse/IGNITE-14686 Project: Ignite Issue Type: Bug Components: python, thin client Reporter: Robert Emanuele The method "get_all" in the thin client's Cache class has a return type hint of a 'list' where in reality it returns a 'dict'. (This is also described in the doc strings correctly as returning a 'dict'.) [https://github.com/apache/ignite-python-thin-client/blob/master/pyignite/cache.py#L256] This would be a simple type hint correction. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14685) Server crashes if joining node has static cache with a duplicate index
[ https://issues.apache.org/jira/browse/IGNITE-14685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339849#comment-17339849 ] Stanislav Lukyanov commented on IGNITE-14685: - Attached a reproducer. In DuplicateIndexTest, testStaticCaches and testServerDynamicClientStaticCaches fail. > Server crashes if joining node has static cache with a duplicate index > -- > > Key: IGNITE-14685 > URL: https://issues.apache.org/jira/browse/IGNITE-14685 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.10 >Reporter: Stanislav Lukyanov >Priority: Major > Attachments: DuplicateIndexTest.java > > > Scenario > # Start a server > # Create a cache FOO with an index named IDX and a schema named BAR > # Start a client with a statically configured cache FOO2 with an index named > IDX and a schema named BAR > Expected result: either client is not allowed to join, or the cache FOO2 is > not created. > Result: server crashes. > {code} > [SEVERE][exchange-worker-#61%sqltests.DuplicateIndexTest0%][] 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: Duplicate index name [cache=foo2, > schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2]]] > class org.apache.ignite.IgniteCheckedException: Duplicate index name > [cache=foo2, schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2] > at > org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7613) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:209) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3405) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3199) > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) > at java.lang.Thread.run(Thread.java:748) > Caused by: class org.apache.ignite.IgniteException: Duplicate index name > [cache=foo2, schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2] > at > org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:2155) > at > org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:1024) > at > org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:1091) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1967) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$55a0e703$1(GridCacheProcessor.java:1837) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$13(GridCacheProcessor.java:1789) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1834) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1788) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.startReceivedCaches(GridCacheProcessor.java:1769) > at > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:965) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3377) > ... 3 more > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14685) Server crashes if joining node has static cache with a duplicate index
[ https://issues.apache.org/jira/browse/IGNITE-14685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov updated IGNITE-14685: Attachment: DuplicateIndexTest.java > Server crashes if joining node has static cache with a duplicate index > -- > > Key: IGNITE-14685 > URL: https://issues.apache.org/jira/browse/IGNITE-14685 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.10 >Reporter: Stanislav Lukyanov >Priority: Major > Attachments: DuplicateIndexTest.java > > > Scenario > # Start a server > # Create a cache FOO with an index named IDX and a schema named BAR > # Start a client with a statically configured cache FOO2 with an index named > IDX and a schema named BAR > Expected result: either client is not allowed to join, or the cache FOO2 is > not created. > Result: server crashes. > {code} > [SEVERE][exchange-worker-#61%sqltests.DuplicateIndexTest0%][] 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: Duplicate index name [cache=foo2, > schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2]]] > class org.apache.ignite.IgniteCheckedException: Duplicate index name > [cache=foo2, schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2] > at > org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7613) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:209) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3405) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3199) > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) > at java.lang.Thread.run(Thread.java:748) > Caused by: class org.apache.ignite.IgniteException: Duplicate index name > [cache=foo2, schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2] > at > org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:2155) > at > org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:1024) > at > org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:1091) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1967) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$55a0e703$1(GridCacheProcessor.java:1837) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$13(GridCacheProcessor.java:1789) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1834) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1788) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.startReceivedCaches(GridCacheProcessor.java:1769) > at > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:965) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3377) > ... 3 more > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14685) Server crashes if joining node has static cache with a duplicate index
[ https://issues.apache.org/jira/browse/IGNITE-14685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov updated IGNITE-14685: Ignite Flags: (was: Docs Required,Release Notes Required) > Server crashes if joining node has static cache with a duplicate index > -- > > Key: IGNITE-14685 > URL: https://issues.apache.org/jira/browse/IGNITE-14685 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.10 >Reporter: Stanislav Lukyanov >Priority: Major > > Scenario > # Start a server > # Create a cache FOO with an index named IDX and a schema named BAR > # Start a client with a statically configured cache FOO2 with an index named > IDX and a schema named BAR > Expected result: either client is not allowed to join, or the cache FOO2 is > not created. > Result: server crashes. > {code} > [SEVERE][exchange-worker-#61%sqltests.DuplicateIndexTest0%][] 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: Duplicate index name [cache=foo2, > schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2]]] > class org.apache.ignite.IgniteCheckedException: Duplicate index name > [cache=foo2, schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2] > at > org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7613) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:209) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3405) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3199) > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) > at java.lang.Thread.run(Thread.java:748) > Caused by: class org.apache.ignite.IgniteException: Duplicate index name > [cache=foo2, schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2] > at > org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:2155) > at > org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:1024) > at > org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:1091) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1967) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$55a0e703$1(GridCacheProcessor.java:1837) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$13(GridCacheProcessor.java:1789) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1834) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1788) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.startReceivedCaches(GridCacheProcessor.java:1769) > at > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:965) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3377) > ... 3 more > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14685) Server crashes if joining node has static cache with a duplicate index
Stanislav Lukyanov created IGNITE-14685: --- Summary: Server crashes if joining node has static cache with a duplicate index Key: IGNITE-14685 URL: https://issues.apache.org/jira/browse/IGNITE-14685 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.10 Reporter: Stanislav Lukyanov Scenario # Start a server # Create a cache FOO with an index named IDX and a schema named BAR # Start a client with a statically configured cache FOO2 with an index named IDX and a schema named BAR Expected result: either client is not allowed to join, or the cache FOO2 is not created. Result: server crashes. {code} [SEVERE][exchange-worker-#61%sqltests.DuplicateIndexTest0%][] 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: Duplicate index name [cache=foo2, schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2]]] class org.apache.ignite.IgniteCheckedException: Duplicate index name [cache=foo2, schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2] at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7613) at org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260) at org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:209) at org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3405) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3199) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) at java.lang.Thread.run(Thread.java:748) Caused by: class org.apache.ignite.IgniteException: Duplicate index name [cache=foo2, schemaName=BAR, idxName=IDX, existingTable=VAL, table=VAL2] at org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:2155) at org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:1024) at org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:1091) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1967) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$55a0e703$1(GridCacheProcessor.java:1837) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$13(GridCacheProcessor.java:1789) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1834) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1788) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startReceivedCaches(GridCacheProcessor.java:1769) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:965) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3377) ... 3 more {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14624) WalSegmentSyncer stops in an incorrect way
[ https://issues.apache.org/jira/browse/IGNITE-14624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339770#comment-17339770 ] Ignite TC Bot commented on IGNITE-14624: {panel:title=Branch: [pull/9080/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} {panel:title=Branch: [pull/9080/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel} [TeamCity *-- Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5994408buildTypeId=IgniteTests24Java8_RunAll] > WalSegmentSyncer stops in an incorrect way > -- > > Key: IGNITE-14624 > URL: https://issues.apache.org/jira/browse/IGNITE-14624 > Project: Ignite > Issue Type: Bug >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > {{WalSegmentSyncer#shutdown}} uses {{U.join(GridWorker, IgniteLogger)}} > method which delegates to {{GridWorker#join()}} > {code:java|title=GridWorker.java} > public void join() throws InterruptedException { > ... > if ((runner == null && isCancelled) || finished) > return; > synchronized (mux) { > while (!finished) > mux.wait(); > } > } > {code} > On the other hand, {{GridWorker#run()}} nullifies the {{runner}} field > *after* the worker notifies all threads that work is finished: > {code:java|title=GridWorker.java} > @Override public final void run() { > // Runner thread must be recorded first as other operations > // may depend on it being present. > runner = Thread.currentThread(); > try { > ... > body(); > } > catch (Throwable e) { > ... > } > finally { > synchronized (mux) { > finished = true; > mux.notifyAll(); > } > ... > // Need to set runner to null, to make sure that > // further operations on this runnable won't > // affect the thread which could have been recycled > // by thread pool. > runner = null; > } > } > {code} > This can lead to {{AssertionError}} like the following: > {noformat} > java.lang.AssertionError: WalSegmentSyncer is running. > > org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl$WalSegmentSyncer.restart(FileHandleManagerImpl.java:646) > > org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FileHandleManagerImpl.resumeLogging(FileHandleManagerImpl.java:235) > > org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.resumeLogging(FileWriteAheadLogManager.java:705) > > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.resumeWalLogging(GridCacheDatabaseSharedManager.java:1707) > > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.finishRecovery(GridCacheDatabaseSharedManager.java:757) > > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.onActivate(GridCacheDatabaseSharedManager.java:637) > > org.apache.ignite.internal.processors.cache.GridCacheSharedContext.activate(GridCacheSharedContext.java:296) > > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:1322) > > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:964) > > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3375) > > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3194) > > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) > java.lang.Thread.run(Thread.java:748) > {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14557) Improve row layout.
[ https://issues.apache.org/jira/browse/IGNITE-14557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339752#comment-17339752 ] Konstantin Orlov commented on IGNITE-14557: --- LGTM! > Improve row layout. > --- > > Key: IGNITE-14557 > URL: https://issues.apache.org/jira/browse/IGNITE-14557 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > h3. Motivation. > When one try to read a column value from a row, the very first check will be > a null-check. > As Null-Table resides right after an Offset-Table, the we need 2 jumps to for > the null-check. > h3. Description. > Assuming, Null-Table reserves a bit for each columns even if the columns is > not Nullable, > Null-table has constant size (within same version of schema) and we no need > extra bytes to persist it's length into the tuple. > * Null-checks will not require extra read for Offset-Table size and extra > jump. > * Offset-Table will not need extra read/jump to reach as Null-Table size is > constant. > Let's just swap these tables in layout and fix docs README.md and IEP. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14583) Server node fails on remote filter deployment after client reconnect with new node id
[ https://issues.apache.org/jira/browse/IGNITE-14583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Belyakov updated IGNITE-14583: --- Reviewer: Alexey Scherbakov > Server node fails on remote filter deployment after client reconnect with new > node id > - > > Key: IGNITE-14583 > URL: https://issues.apache.org/jira/browse/IGNITE-14583 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Igor Belyakov >Assignee: Igor Belyakov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Cluster contains 1 server and 1 client node. PeerClassLoading turned on. > *1.* Client node deploys CQ with remote filter, server node doesn't have > classes required for remote filter in classpath. > *2.* Remote filter successfully deployed to server node. > *3.* Client node disconnects and reconnects by using new node id: > [15:44:43] Client node was reconnected after it was already considered failed > by the server topology (this could happen after all servers restarted or due > to a long network outage between the client and servers). All continuous > queries and remote event listeners created by this client will be > unsubscribed, consider listening to EVT_CLIENT_NODE_RECONNECTED event to > restore them. > *4.* On connect, client node tries to deploy remote filter to server node, > but server node fails due to wrong ClassLoaderId, which is sent in > GridDeploymentInfo (used ClassLoaderId for old client node): > {code:java} > [15:44:42] (err) Failed to notify listener: > o.a.i.i.util.future.GridFutureChainListener@778d0fc6class > org.apache.ignite.IgniteException: Failed to initialize a remote filter. > at > org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.lambda$register$2bf956f5$1(CacheContinuousQueryHandler.java:353) > at > org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:77) > at > org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:69) > at > org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:29) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:398) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:346) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:334) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:510) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:489) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:477) > at > org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1311) > at > org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1283) > at > org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.run(GridContinuousProcessor.java:693) > at > org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7162) > 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: class > org.apache.ignite.internal.IgniteDeploymentCheckedException: Failed to obtain > deployment for class: Client1$$Lambda$513/0x0008003b8840 > at > org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryDeployableObject.unmarshal(CacheContinuousQueryDeployableObject.java:94) > at > org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1308) > ... 8 more > авг. 07, 2020 3:44:42 PM org.apache.ignite.logger.java.JavaLogger error > SEVERE: Failed to unmarshal continuous routine handler > [routineId=8f0137dc-cb32-40ff-83f4-867f272d338e, > srcNodeId=ebcf4d5b-a476-43d5-b057-00b5694104e6] > class org.apache.ignite.internal.IgniteDeploymentCheckedException: Failed to > obtain deployment for class: Client1$$Lambda$513/0x0008003b8840 > at >
[jira] [Assigned] (IGNITE-10745) SQL: jdbc metadata's getColumns returns wrong value for "ORDINAL_POSITION"
[ https://issues.apache.org/jira/browse/IGNITE-10745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-10745: Assignee: Yury Gerzhedovich (was: Alexander Lapin) > SQL: jdbc metadata's getColumns returns wrong value for "ORDINAL_POSITION" > --- > > Key: IGNITE-10745 > URL: https://issues.apache.org/jira/browse/IGNITE-10745 > Project: Ignite > Issue Type: Bug > Components: jdbc, sql >Reporter: Pavel Kuznetsov >Assignee: Yury Gerzhedovich >Priority: Minor > Labels: jdbc, metadata, sql > > Affected both thin and jdbc v2 drivers. > jdbc spec says : > {noformat} > ORDINAL_POSITION int => index of column in table (starting at 1) > {noformat} > but in fact it is a position in the metadata table itself, not position in > the original table. > For example we have table > {code:sql} > Person(id int primary key, val1 int, val2 bigint, val3 int) > {code} > Oridinal number for {{val3}} is 4, but if we specified patterns that leave > only 1 result ({{PUBLIC.Person.val3}}) returned value will be 1. If we > select 2 columns by pattern - 2 or 1 and so on. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14682) Sender is null when sending a message to the local member through the Messaging Service
[ https://issues.apache.org/jira/browse/IGNITE-14682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-14682: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Sender is null when sending a message to the local member through the > Messaging Service > --- > > Key: IGNITE-14682 > URL: https://issues.apache.org/jira/browse/IGNITE-14682 > Project: Ignite > Issue Type: Bug > Components: messaging >Affects Versions: 3.0.0-alpha2 >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Minor > Fix For: 3.0.0-alpha2 > > > When sending a message from a node to itself, {{sender}} parameter in the > messaging event will be {{null.}} > The cause of the error is that the {{memberAddressMap}} does not contain the > local node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14682) Sender is null when sending a message to the local member through the Messaging Service
[ https://issues.apache.org/jira/browse/IGNITE-14682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339720#comment-17339720 ] Semyon Danilov commented on IGNITE-14682: - LGTM! > Sender is null when sending a message to the local member through the > Messaging Service > --- > > Key: IGNITE-14682 > URL: https://issues.apache.org/jira/browse/IGNITE-14682 > Project: Ignite > Issue Type: Bug > Components: messaging >Affects Versions: 3.0.0-alpha2 >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Minor > Fix For: 3.0.0-alpha2 > > > When sending a message from a node to itself, {{sender}} parameter in the > messaging event will be {{null.}} > The cause of the error is that the {{memberAddressMap}} does not contain the > local node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14557) Improve row layout.
[ https://issues.apache.org/jira/browse/IGNITE-14557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339718#comment-17339718 ] Andrey Mashenkov commented on IGNITE-14557: --- [~korlov], fixed. > Improve row layout. > --- > > Key: IGNITE-14557 > URL: https://issues.apache.org/jira/browse/IGNITE-14557 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > h3. Motivation. > When one try to read a column value from a row, the very first check will be > a null-check. > As Null-Table resides right after an Offset-Table, the we need 2 jumps to for > the null-check. > h3. Description. > Assuming, Null-Table reserves a bit for each columns even if the columns is > not Nullable, > Null-table has constant size (within same version of schema) and we no need > extra bytes to persist it's length into the tuple. > * Null-checks will not require extra read for Offset-Table size and extra > jump. > * Offset-Table will not need extra read/jump to reach as Null-Table size is > constant. > Let's just swap these tables in layout and fix docs README.md and IEP. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339709#comment-17339709 ] Eduard Rakhmankulov commented on IGNITE-14469: -- [~sergeychugunov] please look > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14469: - Reviewer: Sergey Chugunov (was: Sergey Chugunov) > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339706#comment-17339706 ] Eduard Rakhmankulov commented on IGNITE-14469: -- [~sergey-chugunov] please look > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14469: - Component/s: (was: sql) > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14469: - Reviewer: Sergey Chugunov > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-14469: - Reviewer: (was: Kirill Tkalenko) > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339705#comment-17339705 ] Kirill Tkalenko commented on IGNITE-14469: -- [~erixon] LGTM. > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14582) Continuous Query deploys remote filter even on client nodes
[ https://issues.apache.org/jira/browse/IGNITE-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Belyakov updated IGNITE-14582: --- Reviewer: Slava Koptilin > Continuous Query deploys remote filter even on client nodes > --- > > Key: IGNITE-14582 > URL: https://issues.apache.org/jira/browse/IGNITE-14582 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Igor Belyakov >Assignee: Igor Belyakov >Priority: Major > Attachments: CacheContinuousQueryDeploymentToClientTest.java > > Time Spent: 10m > Remaining Estimate: 0h > > When the client node joins cluster CQ routine is deployed on it, but there's > no sense to have CQ on the client node which doesn't store any data at all. > Test attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14557) Improve row layout.
[ https://issues.apache.org/jira/browse/IGNITE-14557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339694#comment-17339694 ] Konstantin Orlov commented on IGNITE-14557: --- Hi, [~amashenkov], I left a few minor comments. Please see PR. > Improve row layout. > --- > > Key: IGNITE-14557 > URL: https://issues.apache.org/jira/browse/IGNITE-14557 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > h3. Motivation. > When one try to read a column value from a row, the very first check will be > a null-check. > As Null-Table resides right after an Offset-Table, the we need 2 jumps to for > the null-check. > h3. Description. > Assuming, Null-Table reserves a bit for each columns even if the columns is > not Nullable, > Null-table has constant size (within same version of schema) and we no need > extra bytes to persist it's length into the tuple. > * Null-checks will not require extra read for Offset-Table size and extra > jump. > * Offset-Table will not need extra read/jump to reach as Null-Table size is > constant. > Let's just swap these tables in layout and fix docs README.md and IEP. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14584) Server node fails on remote filter with static initializer deployment if client disconnects
[ https://issues.apache.org/jira/browse/IGNITE-14584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14584: -- Fix Version/s: 2.11 > Server node fails on remote filter with static initializer deployment if > client disconnects > --- > > Key: IGNITE-14584 > URL: https://issues.apache.org/jira/browse/IGNITE-14584 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Igor Belyakov >Assignee: Igor Belyakov >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > Cluster contains 1 server and 1 client node. PeerClassLoading is turned on. > 1. Client node deploys CQ with remote filter, server node doesn't have > classes required for remote filter in classpath. Remote filter should has a > class with static initializer, which has a type that should be deployed: > > {code:java} > public class TestClass { > static { > TestSubClass testSubClass = new TestSubClass(); > } > } > public class TestSubClass { > } > {code} > > 2. When TestSubClass deployment is in progress on the server node, the client > node is stopped > 3. The server node is unable to deploy TestSubClass and static initializer > can't be finished, as result java.lang.ExceptionInInitializerError happens in > discovery thread and server node fails: > {code:java} > [16:56:23,829][WARNING][disco-notifier-worker-#49%srv1%][GridDeploymentPerVersionStore] > Failed to send class-loading request to node (is node alive?) > [node=72513f9a-8053-410c-bc4f-aa4935e06661, clsName=TestSubClass, > clsPath=TestSubClass.class, > clsLdrId=1ca6c09f471-72513f9a-8053-410c-bc4f-aa4935e06661, > parentClsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2][16:56:23,829][WARNING][disco-notifier-worker-#49%srv1%][GridDeploymentPerVersionStore] > Failed to send class-loading request to node (is node alive?) > [node=72513f9a-8053-410c-bc4f-aa4935e06661, clsName=TestSubClass, > clsPath=TestSubClass.class, > clsLdrId=1ca6c09f471-72513f9a-8053-410c-bc4f-aa4935e06661, > parentClsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2] > [16:56:23,829][SEVERE][disco-notifier-worker-#49%srv1%][GridDiscoveryManager] > Exception in discovery notifier worker > thread.java.lang.ExceptionInInitializerError at > java.lang.Class.forName0(Native Method) at > java.lang.Class.forName(Class.java:348) at > org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:9066) at > org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:325) > at > org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:640) > at > org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1755) > at > org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714) > at > org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1976) > at > org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:702) > at > org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:187) > at > org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:887) > at > org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762) > at > org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714) > at > org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:315) > at > org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:300) > at > org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100) > at > org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:80) > at > org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10573) > at > org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10602) > at > org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryDeployableObject.unmarshal(CacheContinuousQueryDeployableObject.java:96) > at > org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1308) > at > org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1283) > at > org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1408) > at >
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339691#comment-17339691 ] Eduard Rakhmankulov commented on IGNITE-14469: -- [~ktkale...@gridgain.com] Checkstyle suite run https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyle/5994954 > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14682) Sender is null when sending a message to the local member through the Messaging Service
[ https://issues.apache.org/jira/browse/IGNITE-14682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339684#comment-17339684 ] Aleksandr Polovtcev commented on IGNITE-14682: -- https://github.com/apache/ignite-3/pull/119 > Sender is null when sending a message to the local member through the > Messaging Service > --- > > Key: IGNITE-14682 > URL: https://issues.apache.org/jira/browse/IGNITE-14682 > Project: Ignite > Issue Type: Bug > Components: messaging >Affects Versions: 3.0.0-alpha2 >Reporter: Aleksandr Polovtcev >Assignee: Aleksandr Polovtcev >Priority: Minor > Fix For: 3.0.0-alpha2 > > > When sending a message from a node to itself, {{sender}} parameter in the > messaging event will be {{null.}} > The cause of the error is that the {{memberAddressMap}} does not contain the > local node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14684) Stopping node at the end of checkpoint can cause "Critical system error"
[ https://issues.apache.org/jira/browse/IGNITE-14684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Makedonskaya updated IGNITE-14684: Description: Checkpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stopping. Run test(see exception in log):org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest#testDestroyTaskLifecycle {noformat} [2021-05-05 15:41:10,907][ERROR][db-checkpoint-thread-#87%db.LongDestroyDurableBackgroundTaskTest0%][root] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to perform cache update: node is stopping.]] class org.apache.ignite.IgniteException: Failed to perform cache update: node is stopping. at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.checkpointReadLock(CheckpointTimeoutLock.java:127) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1583) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.metaStorageOperation(DurableBackgroundTasksProcessor.java:335) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.afterCheckpointEnd(DurableBackgroundTasksProcessor.java:152) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointWorkflow.markCheckpointEnd(CheckpointWorkflow.java:606) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.doCheckpoint(Checkpointer.java:479) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.body(Checkpointer.java:282) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) at java.lang.Thread.run(Thread.java:748) Caused by: class org.apache.ignite.internal.NodeStoppingException: Failed to perform cache update: node is stopping. ... 9 more {noformat} was: Checkpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stoppingCheckpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stopping Run test(see exception in log):org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest#testDestroyTaskLifecycle {noformat} [2021-05-05 15:41:10,907][ERROR][db-checkpoint-thread-#87%db.LongDestroyDurableBackgroundTaskTest0%][root] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to perform cache update: node is stopping.]] class org.apache.ignite.IgniteException: Failed to perform cache update: node is stopping. at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.checkpointReadLock(CheckpointTimeoutLock.java:127) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1583) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.metaStorageOperation(DurableBackgroundTasksProcessor.java:335) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.afterCheckpointEnd(DurableBackgroundTasksProcessor.java:152) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointWorkflow.markCheckpointEnd(CheckpointWorkflow.java:606) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.doCheckpoint(Checkpointer.java:479) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.body(Checkpointer.java:282) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) at java.lang.Thread.run(Thread.java:748) Caused by: class org.apache.ignite.internal.NodeStoppingException: Failed to perform cache update: node is stopping. ... 9
[jira] [Updated] (IGNITE-14684) Stopping node at the end of checkpoint can cause "Critical system error"
[ https://issues.apache.org/jira/browse/IGNITE-14684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Makedonskaya updated IGNITE-14684: Description: Checkpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stoppingCheckpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stopping Run test(see exception in log):org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest#testDestroyTaskLifecycle {noformat} [2021-05-05 15:41:10,907][ERROR][db-checkpoint-thread-#87%db.LongDestroyDurableBackgroundTaskTest0%][root] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to perform cache update: node is stopping.]] class org.apache.ignite.IgniteException: Failed to perform cache update: node is stopping. at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.checkpointReadLock(CheckpointTimeoutLock.java:127) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1583) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.metaStorageOperation(DurableBackgroundTasksProcessor.java:335) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.afterCheckpointEnd(DurableBackgroundTasksProcessor.java:152) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointWorkflow.markCheckpointEnd(CheckpointWorkflow.java:606) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.doCheckpoint(Checkpointer.java:479) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.body(Checkpointer.java:282) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) at java.lang.Thread.run(Thread.java:748) Caused by: class org.apache.ignite.internal.NodeStoppingException: Failed to perform cache update: node is stopping. ... 9 more {noformat} was: Checkpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stoppingCheckpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stopping Run test(see exception in log):org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest#testDestroyTaskLifecycle {noformat} [2021-05-05 15:41:10,907][ERROR][db-checkpoint-thread-#87%db.LongDestroyDurableBackgroundTaskTest0%|#87%db.LongDestroyDurableBackgroundTaskTest0%][root] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to perform cache update: node is stopping.]]class org.apache.ignite.IgniteException: Failed to perform cache update: node is stopping. at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.checkpointReadLock(CheckpointTimeoutLock.java:127) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1583) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.metaStorageOperation(DurableBackgroundTasksProcessor.java:335) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.afterCheckpointEnd(DurableBackgroundTasksProcessor.java:152) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointWorkflow.markCheckpointEnd(CheckpointWorkflow.java:606) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.doCheckpoint(Checkpointer.java:479) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.body(Checkpointer.java:282) at
[jira] [Updated] (IGNITE-14684) Stopping node at the end of checkpoint can cause "Critical system error"
[ https://issues.apache.org/jira/browse/IGNITE-14684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Makedonskaya updated IGNITE-14684: Description: Checkpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stoppingCheckpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stopping Run test(see exception in log):org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest#testDestroyTaskLifecycle {noformat} [2021-05-05 15:41:10,907][ERROR][db-checkpoint-thread-#87%db.LongDestroyDurableBackgroundTaskTest0%|#87%db.LongDestroyDurableBackgroundTaskTest0%][root] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to perform cache update: node is stopping.]]class org.apache.ignite.IgniteException: Failed to perform cache update: node is stopping. at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.checkpointReadLock(CheckpointTimeoutLock.java:127) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1583) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.metaStorageOperation(DurableBackgroundTasksProcessor.java:335) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.afterCheckpointEnd(DurableBackgroundTasksProcessor.java:152) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointWorkflow.markCheckpointEnd(CheckpointWorkflow.java:606) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.doCheckpoint(Checkpointer.java:479) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.body(Checkpointer.java:282) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) at java.lang.Thread.run(Thread.java:748)Caused by: class org.apache.ignite.internal.NodeStoppingException: Failed to perform cache update: node is stopping. ... 9 more {noformat} was: Checkpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stoppingCheckpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stopping Run test(see exception in log):org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest#testDestroyTaskLifecycle {noformat}[2021-05-05 15:41:10,907][ERROR][db-checkpoint-thread-#87%db.LongDestroyDurableBackgroundTaskTest0%][root] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to perform cache update: node is stopping.]]class org.apache.ignite.IgniteException: Failed to perform cache update: node is stopping. at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.checkpointReadLock(CheckpointTimeoutLock.java:127) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1583) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.metaStorageOperation(DurableBackgroundTasksProcessor.java:335) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.afterCheckpointEnd(DurableBackgroundTasksProcessor.java:152) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointWorkflow.markCheckpointEnd(CheckpointWorkflow.java:606) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.doCheckpoint(Checkpointer.java:479) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.body(Checkpointer.java:282) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) at java.lang.Thread.run(Thread.java:748)Caused
[jira] [Created] (IGNITE-14684) Stopping node at the end of checkpoint can cause "Critical system error"
Maria Makedonskaya created IGNITE-14684: --- Summary: Stopping node at the end of checkpoint can cause "Critical system error" Key: IGNITE-14684 URL: https://issues.apache.org/jira/browse/IGNITE-14684 Project: Ignite Issue Type: Bug Components: persistence Reporter: Maria Makedonskaya Assignee: Kirill Tkalenko Checkpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stoppingCheckpoint listener org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor#afterCheckpointEnd which trigger at the end of checkpoint process can not take checkpoint read lock during node stopping Run test(see exception in log):org.apache.ignite.internal.processors.cache.persistence.db.LongDestroyDurableBackgroundTaskTest#testDestroyTaskLifecycle {noformat}[2021-05-05 15:41:10,907][ERROR][db-checkpoint-thread-#87%db.LongDestroyDurableBackgroundTaskTest0%][root] Critical system error detected. Will be handled accordingly to configured handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to perform cache update: node is stopping.]]class org.apache.ignite.IgniteException: Failed to perform cache update: node is stopping. at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointTimeoutLock.checkpointReadLock(CheckpointTimeoutLock.java:127) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1583) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.metaStorageOperation(DurableBackgroundTasksProcessor.java:335) at org.apache.ignite.internal.processors.localtask.DurableBackgroundTasksProcessor.afterCheckpointEnd(DurableBackgroundTasksProcessor.java:152) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointWorkflow.markCheckpointEnd(CheckpointWorkflow.java:606) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.doCheckpoint(Checkpointer.java:479) at org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.body(Checkpointer.java:282) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) at java.lang.Thread.run(Thread.java:748)Caused by: class org.apache.ignite.internal.NodeStoppingException: Failed to perform cache update: node is stopping. ... 9 more\{noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14683) Binary type registration fails when class present in different packages with simple name mapper
[ https://issues.apache.org/jira/browse/IGNITE-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339663#comment-17339663 ] Ilya Kasnacheev commented on IGNITE-14683: -- It may seem that Ignite need to map simple type to complete type, but if query entities/indexed types are used, complete type is known to Ignite anyway, for a specific cache. So no collision may indeed happen unless the types are stored in the same cache (which they were not). > Binary type registration fails when class present in different packages with > simple name mapper > --- > > Key: IGNITE-14683 > URL: https://issues.apache.org/jira/browse/IGNITE-14683 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Major > > The following exception will be caught: > IgniteCheckedException: Failed to merge new and existing marshaller mappings. > For [platformId=0, typeId=12345689] new > typeName=com.pany.services.restApi.ContactList, existing > typeName=com.pany.services.handler.Contactlist > It is expected that there is no metadata conflict and simple name is always > used, if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14683) Binary type registration fails when class present in different packages with simple name mapper
[ https://issues.apache.org/jira/browse/IGNITE-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14683: - Description: The following exception will be caught: IgniteCheckedException: Failed to merge new and existing marshaller mappings. For [platformId=0, typeId=12345689] new typeName=com.pany.services.restApi.ContactList, existing typeName=com.pany.services.handler.Contactlist It is expected that there is no metadata conflict and simple name is always used, if possible. was: The following exception will be caught: IgniteCheckedException: Failed to merge new and existing marshaller mappings. For [platformId=0, typeId=12345689] new typeName=com.pany.services.restApi.ContactList, existing typeName=com.pany.services.handler.Contactlist > Binary type registration fails when class present in different packages with > simple name mapper > --- > > Key: IGNITE-14683 > URL: https://issues.apache.org/jira/browse/IGNITE-14683 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Major > > The following exception will be caught: > IgniteCheckedException: Failed to merge new and existing marshaller mappings. > For [platformId=0, typeId=12345689] new > typeName=com.pany.services.restApi.ContactList, existing > typeName=com.pany.services.handler.Contactlist > It is expected that there is no metadata conflict and simple name is always > used, if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14672) SQL objects configuration schemas
[ https://issues.apache.org/jira/browse/IGNITE-14672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14672: -- Labels: iep-54 ignite-3 (was: ) > SQL objects configuration schemas > - > > Key: IGNITE-14672 > URL: https://issues.apache.org/jira/browse/IGNITE-14672 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Major > Labels: iep-54, ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 20m > Remaining Estimate: 0h > > Need to add SQL related schemas into the > {color:#00}TableIndexConfigurationSchema{color} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14683) Binary type registration fails when class present in different packages with simple name mapper
Ilya Kasnacheev created IGNITE-14683: Summary: Binary type registration fails when class present in different packages with simple name mapper Key: IGNITE-14683 URL: https://issues.apache.org/jira/browse/IGNITE-14683 Project: Ignite Issue Type: Bug Components: binary Affects Versions: 2.8 Reporter: Ilya Kasnacheev The following exception will be caught: IgniteCheckedException: Failed to merge new and existing marshaller mappings. For [platformId=0, typeId=12345689] new typeName=com.pany.services.restApi.ContactList, existing typeName=com.pany.services.handler.Contactlist -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14528) AssertionError in GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture:1528
[ https://issues.apache.org/jira/browse/IGNITE-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339576#comment-17339576 ] Ignite TC Bot commented on IGNITE-14528: {panel:title=Branch: [pull/9003/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} {panel:title=Branch: [pull/9003/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel} [TeamCity *-- Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5965278buildTypeId=IgniteTests24Java8_RunAll] > AssertionError in > GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture:1528 > > > Key: IGNITE-14528 > URL: https://issues.apache.org/jira/browse/IGNITE-14528 > Project: Ignite > Issue Type: Bug >Reporter: Denis Chudov >Assignee: Denis Chudov >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > the fall of the node during a rebalance > {code:java} > 2021-01-31 > 07:45:29.174[ERROR][exchange-worker-#168%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite] > 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.AssertionError: RebalanceFuture [grp=CacheGroupContext > [grp=CACHEGROUP_OBJECT_TO_EVICTION_REGISTRY], topVer=AffinityTopologyVersion > [topVer=46, minorTopVer=0], rebalanceId=27299, routines=22, receivedBytes=0, > receivedKeys=0, partitionsLeft=1659, startTime=-1, endTime=-1, > lastCancelledTime=1612068328290, result=true]]] > java.lang.AssertionError: RebalanceFuture [grp=CacheGroupContext > [grp=CACHEGROUP_OBJECT_TO_EVICTION_REGISTRY], topVer=AffinityTopologyVersion > [topVer=46, minorTopVer=0], rebalanceId=27299, routines=22, receivedBytes=0, > receivedKeys=0, partitionsLeft=1659, startTime=-1, endTime=-1, > lastCancelledTime=1612068328290, result=true] > at > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture.ownPartitionsAndFinishFuture(GridDhtPartitionDemander.java:1528) > at > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.finishPreloading(GridDhtPartitionDemander.java:2064) > at > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.finishPreloading(GridDhtPreloader.java:577) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:419) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:3133) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3280) > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3195) > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14682) Sender is null when sending a message to the local member through the Messaging Service
Aleksandr Polovtcev created IGNITE-14682: Summary: Sender is null when sending a message to the local member through the Messaging Service Key: IGNITE-14682 URL: https://issues.apache.org/jira/browse/IGNITE-14682 Project: Ignite Issue Type: Bug Components: messaging Affects Versions: 3.0.0-alpha2 Reporter: Aleksandr Polovtcev Assignee: Aleksandr Polovtcev When sending a message from a node to itself, {{sender}} parameter in the messaging event will be {{null.}} The cause of the error is that the {{memberAddressMap}} does not contain the local node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14678) Remove a note about TLS 1.3 being unsupported from Java quick start
[ https://issues.apache.org/jira/browse/IGNITE-14678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339558#comment-17339558 ] Ilya Kasnacheev commented on IGNITE-14678: -- Thank you for this doc update, I have merged it. > Remove a note about TLS 1.3 being unsupported from Java quick start > --- > > Key: IGNITE-14678 > URL: https://issues.apache.org/jira/browse/IGNITE-14678 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > TLS 1.3 has been supported for a while, so we should remove a note about it > being unsupported from Java quickstart doc. > https://ignite.apache.org/docs/latest/quick-start/java#running-ignite-with-java-11-or-later -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14678) Remove a note about TLS 1.3 being unsupported from Java quick start
[ https://issues.apache.org/jira/browse/IGNITE-14678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14678: - Ignite Flags: (was: Docs Required,Release Notes Required) > Remove a note about TLS 1.3 being unsupported from Java quick start > --- > > Key: IGNITE-14678 > URL: https://issues.apache.org/jira/browse/IGNITE-14678 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > TLS 1.3 has been supported for a while, so we should remove a note about it > being unsupported from Java quickstart doc. > https://ignite.apache.org/docs/latest/quick-start/java#running-ignite-with-java-11-or-later -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339544#comment-17339544 ] Eduard Rakhmankulov commented on IGNITE-14469: -- [~ktkale...@gridgain.com] look again please > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14675) Refactor IgniteAuthenticationProcessor callbacks
[ https://issues.apache.org/jira/browse/IGNITE-14675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339540#comment-17339540 ] Ignite TC Bot commented on IGNITE-14675: {panel:title=Branch: [pull/9079/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} {panel:title=Branch: [pull/9079/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel} [TeamCity *-- Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5994513buildTypeId=IgniteTests24Java8_RunAll] > Refactor IgniteAuthenticationProcessor callbacks > > > Key: IGNITE-14675 > URL: https://issues.apache.org/jira/browse/IGNITE-14675 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Since IgniteAuthenticationProcessor is not treated as a separate processor, > it is needed to refactor explicit IgniteAuthenticationProcessor callbacks > from other processors. Many of them can be eliminated. > For example onActivate method can be replaced with > PartitionsExchangeAware#onDoneBeforeTopologyUnlock > Explicit onLocalJoin method call can be replaced with > discoMgr.localJoinFuture().listen(fut -> onLocalJoin()); > and so on. > It is also possible that this will require changing the startup order of the > IgniteAuthenticationProcessor. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14657) Add README.md to configuration module
[ https://issues.apache.org/jira/browse/IGNITE-14657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339488#comment-17339488 ] Aleksandr Polovtcev commented on IGNITE-14657: -- The patch looks good > Add README.md to configuration module > - > > Key: IGNITE-14657 > URL: https://issues.apache.org/jira/browse/IGNITE-14657 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 3.0.0-alpha1 >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Add README.md to configuration module -- This message was sent by Atlassian Jira (v8.3.4#803005)