[jira] [Updated] (IGNITE-14889) Investigate options for thin client marshalling in 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-14889: Labels: iep-75 (was: ) > Investigate options for thin client marshalling in 3.0 > -- > > Key: IGNITE-14889 > URL: https://issues.apache.org/jira/browse/IGNITE-14889 > Project: Ignite > Issue Type: Task > Components: thin client >Affects Versions: 3.0.0-alpha1 >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Labels: iep-75 > > We need to investigate available options for serialisation/deserialisation > for 3.0 thin client protocol and propose those options for discussion on the > dev list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14773) Implement a method which can get a table or wait until it wasn't initialized
[
https://issues.apache.org/jira/browse/IGNITE-14773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-14773:
-
Reviewer: Vyacheslav Koptilin
> Implement a method which can get a table or wait until it wasn't initialized
>
>
> Key: IGNITE-14773
> URL: https://issues.apache.org/jira/browse/IGNITE-14773
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
> Time Spent: 3h
> Remaining Estimate: 0h
>
> When a try of table creation was invoked in another thread, a client risks
> getting null value until table has been not initialized yet.
> This behavior is available through the public API:
> {code:java}
> ignite.tables().table("tableName");
> {code}
> But client expected to see the table which was fully initialized.
> Need to implement API which waits for table initialization, if it would need,
> and returns it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14892) Bug in GridCacheWriteBehindStore Flusher thread lookup
[ https://issues.apache.org/jira/browse/IGNITE-14892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-14892. -- Resolution: Duplicate > Bug in GridCacheWriteBehindStore Flusher thread lookup > -- > > Key: IGNITE-14892 > URL: https://issues.apache.org/jira/browse/IGNITE-14892 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.8, 2.7.5, 2.7.6, 2.9, 2.8.1, 2.10, 2.9.1 >Reporter: Mike W >Priority: Major > > There's a bug in GridCacheWriteBehindStore in the flusher method. > [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L674] > The logic states there that if flush thread count is not a power of 2, then > perform some math that is not guaranteed to return a positive number. For > example, if you pass this string as a key it returns a negative number: > accb2e8ea33e4a89b4189463cacc3c4e > and then throws an array out of bounds exception when looking up the thread. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14893) Bug in GridCacheWriteBehindStore Flusher thread lookup
[ https://issues.apache.org/jira/browse/IGNITE-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike W updated IGNITE-14893: Description: There's a bug in GridCacheWriteBehindStore in the flusher method. [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L674] The logic states there that if flush thread count is not a power of 2, then perform this math, which is not guaranteed to return a positive number. idx = ((h = key.hashCode()) ^ (h >>> 16)) % flushThreadCnt For example, if you pass this string as a key, it returns a negative number: accb2e8ea33e4a89b4189463cacc3c4e and then throws an array out of bounds exception when looking up the thread. was: There's a bug in GridCacheWriteBehindStore in the flusher method. [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L674] The logic states there that if flush thread count is not a power of 2, then perform some math that is not guaranteed to return a positive number. For example, if you pass this string as a key it returns a negative number: accb2e8ea33e4a89b4189463cacc3c4e and then throws an array out of bounds exception when looking up the thread. > Bug in GridCacheWriteBehindStore Flusher thread lookup > -- > > Key: IGNITE-14893 > URL: https://issues.apache.org/jira/browse/IGNITE-14893 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.8, 2.7.5, 2.7.6, 2.9, 2.8.1, 2.10, 2.9.1 >Reporter: Mike W >Priority: Major > > There's a bug in GridCacheWriteBehindStore in the flusher method. > [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L674] > The logic states there that if flush thread count is not a power of 2, then > perform this math, which is not guaranteed to return a positive number. > > idx = ((h = key.hashCode()) ^ (h >>> 16)) % flushThreadCnt > > For > example, if you pass this string as a key, it returns a negative number: > accb2e8ea33e4a89b4189463cacc3c4e > and then throws an array out of bounds exception when looking up the thread. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14893) Bug in GridCacheWriteBehindStore Flusher thread lookup
Mike W created IGNITE-14893: --- Summary: Bug in GridCacheWriteBehindStore Flusher thread lookup Key: IGNITE-14893 URL: https://issues.apache.org/jira/browse/IGNITE-14893 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.9.1, 2.10, 2.8.1, 2.9, 2.7.6, 2.7.5, 2.8 Reporter: Mike W There's a bug in GridCacheWriteBehindStore in the flusher method. [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L674] The logic states there that if flush thread count is not a power of 2, then perform some math that is not guaranteed to return a positive number. For example, if you pass this string as a key it returns a negative number: accb2e8ea33e4a89b4189463cacc3c4e and then throws an array out of bounds exception when looking up the thread. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14892) Bug in GridCacheWriteBehindStore Flusher thread lookup
Mike W created IGNITE-14892: --- Summary: Bug in GridCacheWriteBehindStore Flusher thread lookup Key: IGNITE-14892 URL: https://issues.apache.org/jira/browse/IGNITE-14892 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.9.1, 2.10, 2.8.1, 2.9, 2.7.6, 2.7.5, 2.8 Reporter: Mike W There's a bug in GridCacheWriteBehindStore in the flusher method. [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L674] The logic states there that if flush thread count is not a power of 2, then perform some math that is not guaranteed to return a positive number. For example, if you pass this string as a key it returns a negative number: accb2e8ea33e4a89b4189463cacc3c4e and then throws an array out of bounds exception when looking up the thread. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13364) Improve index inline defaults
[ https://issues.apache.org/jira/browse/IGNITE-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-13364: Reviewer: Stanislav Lukyanov > Improve index inline defaults > -- > > Key: IGNITE-13364 > URL: https://issues.apache.org/jira/browse/IGNITE-13364 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeniy Rudenko >Assignee: Maksim Timonin >Priority: Major > Fix For: 2.12 > > Time Spent: 50m > Remaining Estimate: 0h > > We need to improve how inline size is calculated by default for > variable-length types. > Currently if a varlength type is encountered inline size just defaults to 10, > which is almost always not enough. > A more sensible behavior would be the following: > 1. Add a fixed default to the inline size calculation for every > variable-length type. For example, if the default inlined size for a string > is 10 then an index like (INT, VARCHAR, VARCHAR, INT) should have inline size > default as 5 + 10 + 10 + 5 = 30 (5 for each int, 10 for each string). > 2. Add special support for VARCHAR_FIXED - if a VARCHAR has known length then > that length is used for inline size calculation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13364) Improve index inline defaults
[ https://issues.apache.org/jira/browse/IGNITE-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360921#comment-17360921 ] Maksim Timonin commented on IGNITE-13364: - Hi [~slukyanov] ! I've submitted a new patch [1] for this ticket. Could you please have a look? [1] https://github.com/apache/ignite/pull/9167 > Improve index inline defaults > -- > > Key: IGNITE-13364 > URL: https://issues.apache.org/jira/browse/IGNITE-13364 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeniy Rudenko >Assignee: Maksim Timonin >Priority: Major > Fix For: 2.12 > > Time Spent: 50m > Remaining Estimate: 0h > > We need to improve how inline size is calculated by default for > variable-length types. > Currently if a varlength type is encountered inline size just defaults to 10, > which is almost always not enough. > A more sensible behavior would be the following: > 1. Add a fixed default to the inline size calculation for every > variable-length type. For example, if the default inlined size for a string > is 10 then an index like (INT, VARCHAR, VARCHAR, INT) should have inline size > default as 5 + 10 + 10 + 5 = 30 (5 for each int, 10 for each string). > 2. Add special support for VARCHAR_FIXED - if a VARCHAR has known length then > that length is used for inline size calculation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14791) Support byte[] configuration values
[ https://issues.apache.org/jira/browse/IGNITE-14791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360919#comment-17360919 ] Ivan Bessonov commented on IGNITE-14791: [~apolovtcev] thank you for this improvement! > Support byte[] configuration values > --- > > Key: IGNITE-14791 > URL: https://issues.apache.org/jira/browse/IGNITE-14791 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 3.0.0-alpha2 >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 50m > Remaining Estimate: 0h > > Right now "smallest" array type that we have is int[], it may not be > convenient for some use-cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14891) Support Next Java LTS (Java 17)
Sergey Kadaner created IGNITE-14891: --- Summary: Support Next Java LTS (Java 17) Key: IGNITE-14891 URL: https://issues.apache.org/jira/browse/IGNITE-14891 Project: Ignite Issue Type: Improvement Reporter: Sergey Kadaner Next Java LTS is right around the corner and many projects already started working on supporting it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14856) "Failed to resolve class name" on server when cache with indexed types is defined on client
[
https://issues.apache.org/jira/browse/IGNITE-14856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360901#comment-17360901
]
Igor Sapego commented on IGNITE-14856:
--
[~ptupitsyn] looks good to me.
> "Failed to resolve class name" on server when cache with indexed types is
> defined on client
> ---
>
> Key: IGNITE-14856
> URL: https://issues.apache.org/jira/browse/IGNITE-14856
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.10, 2.11
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.11
>
> Attachments: IgniteMarshallerCacheSeparateDirectoryTest.java
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Please see attached reproducer test (
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest#testClientCcfgIndexedGetClosure)
> If an indexed types cache is defined on client node's configuration but not
> server, client may put values into cache but server cannot read them despite
> having class on its classpath:
> {code}
> [2021-06-09 16:00:33,611][ERROR][pub-#229%client%][GridJobWorker] Failed to
> execute job [jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> dep=LocalDeployment [super=GridDeployment [ts=1623243633290, depMode=SHARED,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2,
> clsLdrId=8092cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739, userVer=0,
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false,
> undeployed=false, usage=0]],
> taskClsName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> sesId=6992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> startTime=1623243633569, endTime=9223372036854775807,
> taskNodeId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2, closed=false,
> cpSpi=null, failSpi=null, loadSpi=null, usage=1, fullSup=false,
> internal=false, topPred=null, subjId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> mapFut=IgniteFuture [orig=GridFutureAdapter [ignoreInterrupts=false,
> state=INIT, res=null, hash=1341412812]], execName=null],
> jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739]]
> class org.apache.ignite.IgniteException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1849)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:590)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7181)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:584)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:511)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1265)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2078)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:1105)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:637)
> at
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2.call(IgniteMarshallerCacheSeparateDirectoryTest.java:188)
> at
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2.call(IgniteMarshallerCacheSeparateDirectoryTest.java:185)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1846)
> ... 8 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> class name [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7792)
> at
>
[jira] [Created] (IGNITE-14890) Unify a log string with placeholders for various log-library implementation
Vladislav Pyatkov created IGNITE-14890: -- Summary: Unify a log string with placeholders for various log-library implementation Key: IGNITE-14890 URL: https://issues.apache.org/jira/browse/IGNITE-14890 Project: Ignite Issue Type: Improvement Reporter: Vladislav Pyatkov Assignee: Vladislav Pyatkov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14850) Document python thin client transactions
[ https://issues.apache.org/jira/browse/IGNITE-14850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360890#comment-17360890 ] Igor Sapego commented on IGNITE-14850: -- [~ivandasch] looks good to me. > Document python thin client transactions > > > Key: IGNITE-14850 > URL: https://issues.apache.org/jira/browse/IGNITE-14850 > Project: Ignite > Issue Type: Task > Components: documentation, python, thin client >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Labels: documentation, python, thin > Fix For: python-0.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > 1. Create documentation to thin client transactions. > 2. Create examples for sync and async tx api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14888) IgniteJdbcThinDriver fails to initialize on Java 16
[
https://issues.apache.org/jira/browse/IGNITE-14888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kadaner updated IGNITE-14888:
Summary: IgniteJdbcThinDriver fails to initialize on Java 16 (was:
IgniteJdbcThinDriver fails to instantiate on Java 16)
> IgniteJdbcThinDriver fails to initialize on Java 16
> ---
>
> Key: IGNITE-14888
> URL: https://issues.apache.org/jira/browse/IGNITE-14888
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.9.1
>Reporter: Sergey Kadaner
>Priority: Major
>
> I am getting the following error on Java 16:
> {code:java}
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.IgniteJdbcThinDriver
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:466)
> at
> java.sql/java.sql.DriverManager.isDriverAllowed(DriverManager.java:555)
> at
> java.sql/java.sql.DriverManager.isDriverAllowed(DriverManager.java:547)
> at java.sql/java.sql.DriverManager.getDrivers(DriverManager.java:449)
> at java.sql/java.sql.DriverManager.getDrivers(DriverManager.java:426)
> at
> com.zaxxer.hikari.util.DriverDataSource.(DriverDataSource.java:60)
> {code}
> I am not even trying to use the JDBC driver. Unfortunately, Hikari performs
> Class.forName() on all JDBC drivers in the classpath, and I have a dependency
> on ignite-core.jar
> Currently, this issue prevents me from upgrading to Java 16
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14889) Investigate options for thin client marshalling in 3.0
Igor Sapego created IGNITE-14889: Summary: Investigate options for thin client marshalling in 3.0 Key: IGNITE-14889 URL: https://issues.apache.org/jira/browse/IGNITE-14889 Project: Ignite Issue Type: Task Components: thin client Affects Versions: 3.0.0-alpha1 Reporter: Igor Sapego We need to investigate available options for serialisation/deserialisation for 3.0 thin client protocol and propose those options for discussion on the dev list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14856) "Failed to resolve class name" on server when cache with indexed types is defined on client
[
https://issues.apache.org/jira/browse/IGNITE-14856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360880#comment-17360880
]
Ilya Kasnacheev commented on IGNITE-14856:
--
Java side LGTM; I have left just one small code conventions comment.
> "Failed to resolve class name" on server when cache with indexed types is
> defined on client
> ---
>
> Key: IGNITE-14856
> URL: https://issues.apache.org/jira/browse/IGNITE-14856
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.10, 2.11
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.11
>
> Attachments: IgniteMarshallerCacheSeparateDirectoryTest.java
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Please see attached reproducer test (
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest#testClientCcfgIndexedGetClosure)
> If an indexed types cache is defined on client node's configuration but not
> server, client may put values into cache but server cannot read them despite
> having class on its classpath:
> {code}
> [2021-06-09 16:00:33,611][ERROR][pub-#229%client%][GridJobWorker] Failed to
> execute job [jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> dep=LocalDeployment [super=GridDeployment [ts=1623243633290, depMode=SHARED,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2,
> clsLdrId=8092cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739, userVer=0,
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false,
> undeployed=false, usage=0]],
> taskClsName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> sesId=6992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> startTime=1623243633569, endTime=9223372036854775807,
> taskNodeId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2, closed=false,
> cpSpi=null, failSpi=null, loadSpi=null, usage=1, fullSup=false,
> internal=false, topPred=null, subjId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> mapFut=IgniteFuture [orig=GridFutureAdapter [ignoreInterrupts=false,
> state=INIT, res=null, hash=1341412812]], execName=null],
> jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739]]
> class org.apache.ignite.IgniteException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1849)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:590)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7181)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:584)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:511)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1265)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2078)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:1105)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:637)
> at
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2.call(IgniteMarshallerCacheSeparateDirectoryTest.java:188)
> at
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2.call(IgniteMarshallerCacheSeparateDirectoryTest.java:185)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1846)
> ... 8 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> class name [platformId=0, platform=Java, typeId=1438082999]
> at
>
[jira] [Assigned] (IGNITE-14889) Investigate options for thin client marshalling in 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-14889: --- Assignee: Pavel Tupitsyn > Investigate options for thin client marshalling in 3.0 > -- > > Key: IGNITE-14889 > URL: https://issues.apache.org/jira/browse/IGNITE-14889 > Project: Ignite > Issue Type: Task > Components: thin client >Affects Versions: 3.0.0-alpha1 >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > > We need to investigate available options for serialisation/deserialisation > for 3.0 thin client protocol and propose those options for discussion on the > dev list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14856) "Failed to resolve class name" on server when cache with indexed types is defined on client
[
https://issues.apache.org/jira/browse/IGNITE-14856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360877#comment-17360877
]
Pavel Tupitsyn commented on IGNITE-14856:
-
[~isapego][~ilyak] please review.
> "Failed to resolve class name" on server when cache with indexed types is
> defined on client
> ---
>
> Key: IGNITE-14856
> URL: https://issues.apache.org/jira/browse/IGNITE-14856
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.10, 2.11
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.11
>
> Attachments: IgniteMarshallerCacheSeparateDirectoryTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Please see attached reproducer test (
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest#testClientCcfgIndexedGetClosure)
> If an indexed types cache is defined on client node's configuration but not
> server, client may put values into cache but server cannot read them despite
> having class on its classpath:
> {code}
> [2021-06-09 16:00:33,611][ERROR][pub-#229%client%][GridJobWorker] Failed to
> execute job [jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> dep=LocalDeployment [super=GridDeployment [ts=1623243633290, depMode=SHARED,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2,
> clsLdrId=8092cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739, userVer=0,
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false,
> undeployed=false, usage=0]],
> taskClsName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> sesId=6992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> startTime=1623243633569, endTime=9223372036854775807,
> taskNodeId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2, closed=false,
> cpSpi=null, failSpi=null, loadSpi=null, usage=1, fullSup=false,
> internal=false, topPred=null, subjId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> mapFut=IgniteFuture [orig=GridFutureAdapter [ignoreInterrupts=false,
> state=INIT, res=null, hash=1341412812]], execName=null],
> jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739]]
> class org.apache.ignite.IgniteException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1849)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:590)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7181)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:584)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:511)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1265)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2078)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:1105)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:637)
> at
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2.call(IgniteMarshallerCacheSeparateDirectoryTest.java:188)
> at
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2.call(IgniteMarshallerCacheSeparateDirectoryTest.java:185)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1846)
> ... 8 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> class name [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7792)
> at
>
[jira] [Commented] (IGNITE-14856) "Failed to resolve class name" on server when cache with indexed types is defined on client
[
https://issues.apache.org/jira/browse/IGNITE-14856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360873#comment-17360873
]
Ignite TC Bot commented on IGNITE-14856:
{panel:title=Branch: [pull/9163/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}RDD{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042767]]
{panel}
{panel:title=Branch: [pull/9163/head] Base: [master] : New Tests
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 1{color} [[tests
11|https://ci.ignite.apache.org/viewLog.html?buildId=6042771]]
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgIndexedClosure -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testRegular - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testServerCcfgIndexedGetClosure -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgIndexed - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgIndexedPutClosure -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgGetClosure -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testIndexed - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testServerCcfgPutClosure -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testIndexedClosure - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testServerCcfgIndexed - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgIndexedGetClosure -
PASSED{color}
... and 0 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6042552buildTypeId=IgniteTests24Java8_RunAll]
> "Failed to resolve class name" on server when cache with indexed types is
> defined on client
> ---
>
> Key: IGNITE-14856
> URL: https://issues.apache.org/jira/browse/IGNITE-14856
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.10, 2.11
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.11
>
> Attachments: IgniteMarshallerCacheSeparateDirectoryTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Please see attached reproducer test (
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest#testClientCcfgIndexedGetClosure)
> If an indexed types cache is defined on client node's configuration but not
> server, client may put values into cache but server cannot read them despite
> having class on its classpath:
> {code}
> [2021-06-09 16:00:33,611][ERROR][pub-#229%client%][GridJobWorker] Failed to
> execute job [jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> dep=LocalDeployment [super=GridDeployment [ts=1623243633290, depMode=SHARED,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2,
> clsLdrId=8092cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739, userVer=0,
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false,
> undeployed=false, usage=0]],
> taskClsName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> sesId=6992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> startTime=1623243633569, endTime=9223372036854775807,
> taskNodeId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2, closed=false,
> cpSpi=null, failSpi=null, loadSpi=null, usage=1, fullSup=false,
> internal=false, topPred=null, subjId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> mapFut=IgniteFuture [orig=GridFutureAdapter [ignoreInterrupts=false,
> state=INIT, res=null, hash=1341412812]], execName=null],
> jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739]]
> class org.apache.ignite.IgniteException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1849)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:590)
> at
>
[jira] [Issue Comment Deleted] (IGNITE-14856) "Failed to resolve class name" on server when cache with indexed types is defined on client
[
https://issues.apache.org/jira/browse/IGNITE-14856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14856:
Comment: was deleted
(was: {panel:title=Branch: [pull/9163/head] Base: [master] : Possible Blockers
(25)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}RDD{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042476]]
{color:#d04437}Cache 9{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042515]]
{color:#d04437}Basic 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042608]]
{color:#d04437}Binary Objects{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042455]]
{color:#d04437}Platform .NET (Long Running){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6042529]]
* exe: ClientConnectionTest.TestOperationTimeout - Test has low fail rate in
base branch 0,0% and is not flaky
{color:#d04437}Cassandra Store{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042538]]
{color:#d04437}Cache (Full API Multi JVM){color} [[tests
19|https://ci.ignite.apache.org/viewLog.html?buildId=6042502]]
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCacheAtomicClientOnlyMultiJvmFullApiSelfTest.testGetAndRemoveObject - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCacheAtomicClientOnlyMultiJvmFullApiSelfTest.testGlobalRemoveAllAsync -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testTransformReturnValuePutInTx
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testGetAndPutAsyncOld -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testPutxIfAbsentAsyncNoTx
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testGetAndPutIfAbsentAsyncOld
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testPeekTxRemoveOptimistic
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testCacheProxy - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testGetAllWithInTheMiddle
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testGlobalClearAll -
Test has low fail rate in base branch 0,0% and is not flaky
... and 8 tests blockers
{panel}
{panel:title=Branch: [pull/9163/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=6042552buildTypeId=IgniteTests24Java8_RunAll])
> "Failed to resolve class name" on server when cache with indexed types is
> defined on client
> ---
>
> Key: IGNITE-14856
> URL: https://issues.apache.org/jira/browse/IGNITE-14856
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.10, 2.11
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.11
>
> Attachments: IgniteMarshallerCacheSeparateDirectoryTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Please see attached reproducer test (
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest#testClientCcfgIndexedGetClosure)
> If an indexed types cache is defined on client node's configuration but not
> server, client may put values into cache but server cannot read them despite
> having class on its classpath:
> {code}
> [2021-06-09 16:00:33,611][ERROR][pub-#229%client%][GridJobWorker] Failed to
> execute job [jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
>
[jira] [Issue Comment Deleted] (IGNITE-14856) "Failed to resolve class name" on server when cache with indexed types is defined on client
[
https://issues.apache.org/jira/browse/IGNITE-14856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14856:
Comment: was deleted
(was: {panel:title=Branch: [pull/9163/head] Base: [master] : Possible Blockers
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}RDD{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6041999]]
{color:#d04437}Cache (Failover) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042022]]
{color:#d04437}Basic 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6042114]]
* IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgIndexedPutClosure -
History for base branch is absent.
{color:#d04437}Java Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6041993]]
{color:#d04437}PDS 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042046]]
{color:#d04437}Dev Utils{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042064]]
{color:#d04437}~Build{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042290]]
{color:#d04437}Cache (Full API Multi JVM){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6042025]]
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCacheReplicatedMultiJvmFullApiSelfTest.testGlobalRemoveAllAsync - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCacheReplicatedMultiJvmFullApiSelfTest.testRemoveAllSkipStore - Test has
low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9163/head] Base: [master] : New Tests
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Basic 1{color} [[tests
11|https://ci.ignite.apache.org/viewLog.html?buildId=6042114]]
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgIndexedClosure -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testRegular - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testServerCcfgIndexedGetClosure -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgIndexed - PASSED{color}
* {color:#8b}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgIndexedPutClosure -
FAILED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgGetClosure -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testIndexed - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testServerCcfgPutClosure -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testIndexedClosure - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testServerCcfgIndexed - PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
IgniteMarshallerCacheSeparateDirectoryTest.testClientCcfgIndexedGetClosure -
PASSED{color}
... and 0 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6042075buildTypeId=IgniteTests24Java8_RunAll])
> "Failed to resolve class name" on server when cache with indexed types is
> defined on client
> ---
>
> Key: IGNITE-14856
> URL: https://issues.apache.org/jira/browse/IGNITE-14856
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.10, 2.11
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.11
>
> Attachments: IgniteMarshallerCacheSeparateDirectoryTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Please see attached reproducer test (
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest#testClientCcfgIndexedGetClosure)
> If an indexed types cache is defined on client node's configuration but not
> server, client may put values into cache but server cannot read them despite
> having class on its classpath:
> {code}
> [2021-06-09 16:00:33,611][ERROR][pub-#229%client%][GridJobWorker] Failed to
> execute job [jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> dep=LocalDeployment [super=GridDeployment [ts=1623243633290, depMode=SHARED,
>
[jira] [Created] (IGNITE-14888) IgniteJdbcThinDriver fails to instantiate on Java 16
Sergey Kadaner created IGNITE-14888:
---
Summary: IgniteJdbcThinDriver fails to instantiate on Java 16
Key: IGNITE-14888
URL: https://issues.apache.org/jira/browse/IGNITE-14888
Project: Ignite
Issue Type: Bug
Components: jdbc
Affects Versions: 2.9.1
Reporter: Sergey Kadaner
I am getting the following error on Java 16:
{code:java}
Caused by: java.lang.NoClassDefFoundError: Could not initialize class
org.apache.ignite.IgniteJdbcThinDriver
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:466)
at
java.sql/java.sql.DriverManager.isDriverAllowed(DriverManager.java:555)
at
java.sql/java.sql.DriverManager.isDriverAllowed(DriverManager.java:547)
at java.sql/java.sql.DriverManager.getDrivers(DriverManager.java:449)
at java.sql/java.sql.DriverManager.getDrivers(DriverManager.java:426)
at
com.zaxxer.hikari.util.DriverDataSource.(DriverDataSource.java:60)
{code}
I am not even trying to use the JDBC driver. Unfortunately, Hikari performs
Class.forName() on all JDBC drivers in the classpath, and I have a dependency
on ignite-core.jar
Currently, this issue prevents me from upgrading to Java 16
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14887) Need a way to protect public API from stopping node
Vyacheslav Koptilin created IGNITE-14887: Summary: Need a way to protect public API from stopping node Key: IGNITE-14887 URL: https://issues.apache.org/jira/browse/IGNITE-14887 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14408) Vault based on custom persistent storage
[
https://issues.apache.org/jira/browse/IGNITE-14408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-14408:
-
Fix Version/s: 3.0.0-alpha3
> Vault based on custom persistent storage
> -
>
> Key: IGNITE-14408
> URL: https://issues.apache.org/jira/browse/IGNITE-14408
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Vyacheslav Koptilin
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Fix For: 3.0.0-alpha3
>
>
> We can use RocksDB as a persistent layer in order to cover the node restart
> scenario.
> Also let's rename Vault's method {{bootstrapped}} to {{bootstrappedWithPDS}}
> or rename to {{initialized()}} and change the logic in the following way:
> * returns true if was deployed atop PDS with some configuration included;
> * returns true if it was bootstrapped with user bootstrap configuration;
> * returns true if there was no user bootstrap configuration and the default
> one was used.
> Seems that the second option is better.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14408) Vault based on custom persistent storage
[
https://issues.apache.org/jira/browse/IGNITE-14408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-14408:
-
Labels: iep-74 (was: )
> Vault based on custom persistent storage
> -
>
> Key: IGNITE-14408
> URL: https://issues.apache.org/jira/browse/IGNITE-14408
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Vyacheslav Koptilin
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: iep-74
> Fix For: 3.0.0-alpha3
>
>
> We can use RocksDB as a persistent layer in order to cover the node restart
> scenario.
> Also let's rename Vault's method {{bootstrapped}} to {{bootstrappedWithPDS}}
> or rename to {{initialized()}} and change the logic in the following way:
> * returns true if was deployed atop PDS with some configuration included;
> * returns true if it was bootstrapped with user bootstrap configuration;
> * returns true if there was no user bootstrap configuration and the default
> one was used.
> Seems that the second option is better.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13364) Improve index inline defaults
[ https://issues.apache.org/jira/browse/IGNITE-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin reassigned IGNITE-13364: --- Assignee: Maksim Timonin (was: Evgeniy Rudenko) > Improve index inline defaults > -- > > Key: IGNITE-13364 > URL: https://issues.apache.org/jira/browse/IGNITE-13364 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeniy Rudenko >Assignee: Maksim Timonin >Priority: Major > Fix For: 2.12 > > Time Spent: 40m > Remaining Estimate: 0h > > We need to improve how inline size is calculated by default for > variable-length types. > Currently if a varlength type is encountered inline size just defaults to 10, > which is almost always not enough. > A more sensible behavior would be the following: > 1. Add a fixed default to the inline size calculation for every > variable-length type. For example, if the default inlined size for a string > is 10 then an index like (INT, VARCHAR, VARCHAR, INT) should have inline size > default as 5 + 10 + 10 + 5 = 30 (5 for each int, 10 for each string). > 2. Add special support for VARCHAR_FIXED - if a VARCHAR has known length then > that length is used for inline size calculation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14812) SQL statistics
[
https://issues.apache.org/jira/browse/IGNITE-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360828#comment-17360828
]
Ignite TC Bot commented on IGNITE-14812:
{panel:title=Branch: [pull/9145/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9145/head] Base: [master] : New Tests
(176)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests
176|https://ci.ignite.apache.org/viewLog.html?buildId=6041303]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsViewsPersistenceTest.testConfigurationViewDeletion - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsViewsInMemoryTest.testConfigurationViewDeletion - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsConfigurationTest.dropUpdate[persist=true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsConfigurationTest.updateStatisticsOnChangeTopology[persist=false] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsConfigurationTest.updateStatisticsOnChangeTopology[persist=true] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsConfigurationTest.dropSingleColumnStatisticWhileNodeDown[persist=true]
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsConfigurationTest.dropSingleColumnStatisticWhileNodeDown[persist=false]
- PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsConfigurationTest.dropUpdate[persist=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsViewsPersistenceTest.testEnforceStatisticValues - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsViewsInMemoryTest.testEnforceStatisticValues - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
StatisticsConfigurationTest.dropColumnWhileNodeDown[persist=false] -
PASSED{color}
... and 165 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6039241buildTypeId=IgniteTests24Java8_RunAll]
> SQL statistics
> --
>
> Key: IGNITE-14812
> URL: https://issues.apache.org/jira/browse/IGNITE-14812
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Reporter: Alexander Belyak
>Assignee: Alexander Belyak
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add statistics collection and usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14886) Binary metadata registration in EntryProcessor fails after CREATE TABLE with same type
Anton Kurbanov created IGNITE-14886: --- Summary: Binary metadata registration in EntryProcessor fails after CREATE TABLE with same type Key: IGNITE-14886 URL: https://issues.apache.org/jira/browse/IGNITE-14886 Project: Ignite Issue Type: Bug Reporter: Anton Kurbanov Attachments: BinaryObjectEntryProcessorTest.java https://ignite.apache.org/docs/latest/key-value-api/binary-objects#creating-and-modifying-binary-objects This part of documentation assumes that binary object can be processed/created/modified within the EntryProcessor, however in this case it is no longer working unless the type is manually registered before executing the invoke or create table is removed, which renders this documentation part incorrect. This situation happens since the attempt to fix metadata registration deadlock here: https://issues.apache.org/jira/browse/IGNITE-11313 Failing test attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14593) Calcite. Support not equal expression.
[
https://issues.apache.org/jira/browse/IGNITE-14593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360764#comment-17360764
]
Aleksey Plekhanov commented on IGNITE-14593:
Also, the current H2-based SQL engine supports the "!=" operator, and by
supporting it in the calcite-based SQL engine we can minimize compatibility
issues.
To support "!=" we should override {{SqlConformance.isBangEqualAllowed}} method.
> Calcite. Support not equal expression.
> --
>
> Key: IGNITE-14593
> URL: https://issues.apache.org/jira/browse/IGNITE-14593
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Stanilovsky Evgeny
>Priority: Major
> Labels: calcite
>
> Looks like it would be helpful to support "!=" syntax, i.e. :
> {code:java}
> UPDATE test SET a=7 WHERE id != 3
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14849) Calcite engine. Support '%' operator as alias for 'mod' function
[
https://issues.apache.org/jira/browse/IGNITE-14849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360760#comment-17360760
]
Aleksey Plekhanov commented on IGNITE-14849:
[~korlov], [~tledkov-gridgain], can you please have a look?
> Calcite engine. Support '%' operator as alias for 'mod' function
>
>
> Key: IGNITE-14849
> URL: https://issues.apache.org/jira/browse/IGNITE-14849
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the H2-based SQL engine supports both {{a % b}} and {{mod(a, b)}}
> syntax for the modulo operation. But calcite-based engine supports only
> {{mod(a, b)}} syntax. Support for {{%}} operator should be added to minimize
> compatibility issues.
> Affected tests:
> {{src/test/sql/aggregate/group/test_group_by.test}}
> And many other.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14869) Wrong key fields order for recovery index. Leads to CorruptedTreeException
[ https://issues.apache.org/jira/browse/IGNITE-14869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin resolved IGNITE-14869. - Resolution: Duplicate Fixed in https://issues.apache.org/jira/browse/IGNITE-14451 > Wrong key fields order for recovery index. Leads to CorruptedTreeException > -- > > Key: IGNITE-14869 > URL: https://issues.apache.org/jira/browse/IGNITE-14869 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > > Reproducer from user list: > [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashed-with-CorruptedTreeException-tt36173.html] > > Reason is: > # User specified table with fields order (viewId, status); > # User specified primary key with different order (status, viewId); > # Index created with (status, viewId); > # After restart cluster index builds with (viewId, status) due to different > handling of PK fields after recovery (H2TableDescriptor) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14885) Calcite engine. Allow grouping by alias or ordinal
Aleksey Plekhanov created IGNITE-14885:
--
Summary: Calcite engine. Allow grouping by alias or ordinal
Key: IGNITE-14885
URL: https://issues.apache.org/jira/browse/IGNITE-14885
Project: Ignite
Issue Type: Improvement
Reporter: Aleksey Plekhanov
Currently, grouping by alias or ordinal is not supported, but sometimes it can
be handy.
Some DB vendors support this feature (PostgreSQL, MySQL), but some not (Oracle,
MSSQL). In the current Ignite H2-based SQL engine, this feature is not
supported. We should decide do we need it in Ignite with calcite-based SQL
engine.
This feature can be easily enabled by redefining
{{SqlConformance#isGroupByAlias}}, {{SqlConformance#isGroupByOrdinal}}
Affected tests:
{{src/test/sql/aggregate/group/test_group_by.test}}
{{src/test/sql/aggregate/group/test_group_by_alias.test}}
And many other.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14869) Wrong key fields order for recovery index. Leads to CorruptedTreeException
[ https://issues.apache.org/jira/browse/IGNITE-14869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-14869: Description: Reproducer from user list: [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashed-with-CorruptedTreeException-tt36173.html] Reason is: # User specified table with fields order (viewId, status); # User specified primary key with different order (status, viewId); # Index created with (status, viewId); # After restart cluster index builds with (viewId, status) due to different handling of PK fields after recovery (H2TableDescriptor) was: Reproducer from user list: http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashed-with-CorruptedTreeException-tt36173.html > Wrong key fields order for recovery index. Leads to CorruptedTreeException > -- > > Key: IGNITE-14869 > URL: https://issues.apache.org/jira/browse/IGNITE-14869 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > > Reproducer from user list: > [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashed-with-CorruptedTreeException-tt36173.html] > > Reason is: > # User specified table with fields order (viewId, status); > # User specified primary key with different order (status, viewId); > # Index created with (status, viewId); > # After restart cluster index builds with (viewId, status) due to different > handling of PK fields after recovery (H2TableDescriptor) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14869) Wrong key fields order for recovery index. Leads to CorruptedTreeException
[ https://issues.apache.org/jira/browse/IGNITE-14869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-14869: Summary: Wrong key fields order for recovery index. Leads to CorruptedTreeException (was: CorruptedTreeException while reactivate and restart cluster under load.) > Wrong key fields order for recovery index. Leads to CorruptedTreeException > -- > > Key: IGNITE-14869 > URL: https://issues.apache.org/jira/browse/IGNITE-14869 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > > Reproducer from user list: > > http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashed-with-CorruptedTreeException-tt36173.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14883) Managing metastorage group via CLI
Vyacheslav Koptilin created IGNITE-14883: Summary: Managing metastorage group via CLI Key: IGNITE-14883 URL: https://issues.apache.org/jira/browse/IGNITE-14883 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14884) Shutdown policy and well-defined scale down protocol
Vyacheslav Koptilin created IGNITE-14884: Summary: Shutdown policy and well-defined scale down protocol Key: IGNITE-14884 URL: https://issues.apache.org/jira/browse/IGNITE-14884 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14879) Create custom policies to adjust list of data nodes/baseline/table group
Vyacheslav Koptilin created IGNITE-14879: Summary: Create custom policies to adjust list of data nodes/baseline/table group Key: IGNITE-14879 URL: https://issues.apache.org/jira/browse/IGNITE-14879 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14874) Need to define/Introduce consistent identifier term
Vyacheslav Koptilin created IGNITE-14874: Summary: Need to define/Introduce consistent identifier term Key: IGNITE-14874 URL: https://issues.apache.org/jira/browse/IGNITE-14874 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin Currently, ignite node uses "name" as its primary identifier (along with internal id). Need to get an agreement which term should be used: "name", "instanceName", "consistentId" and update code in accordance with it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14878) Introduce table space/group concept
Vyacheslav Koptilin created IGNITE-14878: Summary: Introduce table space/group concept Key: IGNITE-14878 URL: https://issues.apache.org/jira/browse/IGNITE-14878 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14880) Partition loss policies. Provide a useful and convenient way to list unavailable/offline partitions
Vyacheslav Koptilin created IGNITE-14880: Summary: Partition loss policies. Provide a useful and convenient way to list unavailable/offline partitions Key: IGNITE-14880 URL: https://issues.apache.org/jira/browse/IGNITE-14880 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14856) "Failed to resolve class name" on server when cache with indexed types is defined on client
[
https://issues.apache.org/jira/browse/IGNITE-14856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360673#comment-17360673
]
Ignite TC Bot commented on IGNITE-14856:
{panel:title=Branch: [pull/9163/head] Base: [master] : Possible Blockers
(25)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}RDD{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042476]]
{color:#d04437}Cache 9{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042515]]
{color:#d04437}Basic 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042608]]
{color:#d04437}Binary Objects{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042455]]
{color:#d04437}Platform .NET (Long Running){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6042529]]
* exe: ClientConnectionTest.TestOperationTimeout - Test has low fail rate in
base branch 0,0% and is not flaky
{color:#d04437}Cassandra Store{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6042538]]
{color:#d04437}Cache (Full API Multi JVM){color} [[tests
19|https://ci.ignite.apache.org/viewLog.html?buildId=6042502]]
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCacheAtomicClientOnlyMultiJvmFullApiSelfTest.testGetAndRemoveObject - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCacheAtomicClientOnlyMultiJvmFullApiSelfTest.testGlobalRemoveAllAsync -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testTransformReturnValuePutInTx
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testGetAndPutAsyncOld -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testPutxIfAbsentAsyncNoTx
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testGetAndPutIfAbsentAsyncOld
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testPeekTxRemoveOptimistic
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testCacheProxy - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testGetAllWithInTheMiddle
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheFullApiMultiJvmSelfTestSuite:
GridCachePartitionedMultiJvmP2PDisabledFullApiSelfTest.testGlobalClearAll -
Test has low fail rate in base branch 0,0% and is not flaky
... and 8 tests blockers
{panel}
{panel:title=Branch: [pull/9163/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=6042552buildTypeId=IgniteTests24Java8_RunAll]
> "Failed to resolve class name" on server when cache with indexed types is
> defined on client
> ---
>
> Key: IGNITE-14856
> URL: https://issues.apache.org/jira/browse/IGNITE-14856
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.10, 2.11
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.11
>
> Attachments: IgniteMarshallerCacheSeparateDirectoryTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Please see attached reproducer test (
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest#testClientCcfgIndexedGetClosure)
> If an indexed types cache is defined on client node's configuration but not
> server, client may put values into cache but server cannot read them despite
> having class on its classpath:
> {code}
> [2021-06-09 16:00:33,611][ERROR][pub-#229%client%][GridJobWorker] Failed to
> execute job [jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
>
[jira] [Updated] (IGNITE-14877) Introduce API in order to manage metastorage group
[ https://issues.apache.org/jira/browse/IGNITE-14877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14877: - Labels: ignite-3 (was: ) > Introduce API in order to manage metastorage group > -- > > Key: IGNITE-14877 > URL: https://issues.apache.org/jira/browse/IGNITE-14877 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14882) Define minimal list of required metrics to monitor baseline and cluster state
Vyacheslav Koptilin created IGNITE-14882: Summary: Define minimal list of required metrics to monitor baseline and cluster state Key: IGNITE-14882 URL: https://issues.apache.org/jira/browse/IGNITE-14882 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14877) Introduce API in order to manage metastorage group
[ https://issues.apache.org/jira/browse/IGNITE-14877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14877: - Ignite Flags: (was: Docs Required,Release Notes Required) > Introduce API in order to manage metastorage group > -- > > Key: IGNITE-14877 > URL: https://issues.apache.org/jira/browse/IGNITE-14877 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14879) Create custom policies to adjust list of data nodes (baseline nodes)
[ https://issues.apache.org/jira/browse/IGNITE-14879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14879: - Summary: Create custom policies to adjust list of data nodes (baseline nodes) (was: Create custom policies to adjust list of data nodes/baseline/table group) > Create custom policies to adjust list of data nodes (baseline nodes) > > > Key: IGNITE-14879 > URL: https://issues.apache.org/jira/browse/IGNITE-14879 > Project: Ignite > Issue Type: Sub-task >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14876) Define Ignite Cluster API: cluster/node states, run-levels and their semantics
Vyacheslav Koptilin created IGNITE-14876: Summary: Define Ignite Cluster API: cluster/node states, run-levels and their semantics Key: IGNITE-14876 URL: https://issues.apache.org/jira/browse/IGNITE-14876 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14877) Introduce API in order to manage metastorage group
Vyacheslav Koptilin created IGNITE-14877: Summary: Introduce API in order to manage metastorage group Key: IGNITE-14877 URL: https://issues.apache.org/jira/browse/IGNITE-14877 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14881) Managing baseline via CLI
Vyacheslav Koptilin created IGNITE-14881: Summary: Managing baseline via CLI Key: IGNITE-14881 URL: https://issues.apache.org/jira/browse/IGNITE-14881 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14875) Define API of cluster node and move it from network component to the public API
Vyacheslav Koptilin created IGNITE-14875: Summary: Define API of cluster node and move it from network component to the public API Key: IGNITE-14875 URL: https://issues.apache.org/jira/browse/IGNITE-14875 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14873) Failover scenarios
Vyacheslav Koptilin created IGNITE-14873: Summary: Failover scenarios Key: IGNITE-14873 URL: https://issues.apache.org/jira/browse/IGNITE-14873 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin Need to implement a comprehensive set of tests in order to cover data rebalancing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14872) Recalculation affinity based on topology events
Vyacheslav Koptilin created IGNITE-14872: Summary: Recalculation affinity based on topology events Key: IGNITE-14872 URL: https://issues.apache.org/jira/browse/IGNITE-14872 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14209) Data rebalancing
[ https://issues.apache.org/jira/browse/IGNITE-14209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-14209: - Summary: Data rebalancing (was: Need to implement data rebalancing which is required by atomic/transactional caches ) > Data rebalancing > > > Key: IGNITE-14209 > URL: https://issues.apache.org/jira/browse/IGNITE-14209 > Project: Ignite > Issue Type: New Feature >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14871) Provide validation protocol for newly joining nodes.
Vyacheslav Koptilin created IGNITE-14871: Summary: Provide validation protocol for newly joining nodes. Key: IGNITE-14871 URL: https://issues.apache.org/jira/browse/IGNITE-14871 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14870) Define mechanism for collecting and exchanging discovery data when joining a node
Vyacheslav Koptilin created IGNITE-14870: Summary: Define mechanism for collecting and exchanging discovery data when joining a node Key: IGNITE-14870 URL: https://issues.apache.org/jira/browse/IGNITE-14870 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14868) Failed to get jCache proxy of already started cache within transaction while handling thin client request.
[
https://issues.apache.org/jira/browse/IGNITE-14868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-14868:
-
Description:
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example.Assert that cache context exists.
# Get cache instance by name inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
Actually, PME finished at this time and I'd expect that the cache 's
jCacheProxy should be already created
{code}
[2021-06-10 10:39:34,072][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish proxy
initialization, cacheName=tx_cache,
localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
[2021-06-10 10:39:34,073][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
Completed partition exchange
[2021-06-10 10:39:34,075][INFO
][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=284f7bcf-4956-40c2-9df5-de8cac60]
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
{code}
was:
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example.Assert that cache context exists.
# Get cache instance by name inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
Actually, PME finished at this time and I'd expect that the cache 's context
should be already created
{code}
[2021-06-10 10:39:34,072][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish proxy
initialization, cacheName=tx_cache,
localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
[2021-06-10 10:39:34,073][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
Completed partition exchange
[2021-06-10 10:39:34,075][INFO
][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=284f7bcf-4956-40c2-9df5-de8cac60]
Failure in
[jira] [Assigned] (IGNITE-14849) Calcite engine. Support '%' operator as alias for 'mod' function
[
https://issues.apache.org/jira/browse/IGNITE-14849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov reassigned IGNITE-14849:
--
Assignee: Aleksey Plekhanov
> Calcite engine. Support '%' operator as alias for 'mod' function
>
>
> Key: IGNITE-14849
> URL: https://issues.apache.org/jira/browse/IGNITE-14849
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>
> Currently, the H2-based SQL engine supports both {{a % b}} and {{mod(a, b)}}
> syntax for the modulo operation. But calcite-based engine supports only
> {{mod(a, b)}} syntax. Support for {{%}} operator should be added to minimize
> compatibility issues.
> Affected tests:
> {{src/test/sql/aggregate/group/test_group_by.test}}
> And many other.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14868) Failed to get jCache proxy of already started cache within transaction while handling thin client request.
[
https://issues.apache.org/jira/browse/IGNITE-14868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-14868:
-
Description:
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example.Assert that cache context exists.
# Get cache instance by name inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
Actually, PME finished at this time and I'd expect that the cache 's context
should be already created
{code}
[2021-06-10 10:39:34,072][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish proxy
initialization, cacheName=tx_cache,
localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
[2021-06-10 10:39:34,073][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
Completed partition exchange
[2021-06-10 10:39:34,075][INFO
][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=284f7bcf-4956-40c2-9df5-de8cac60]
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
{code}
was:
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example. Get cache instance by name
inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
Actually, PME finished at this time and I'd expect that the cache 's context
should be already created
{code}
[2021-06-10 10:39:34,072][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish proxy
initialization, cacheName=tx_cache,
localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
[2021-06-10 10:39:34,073][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
Completed partition exchange
[2021-06-10 10:39:34,075][INFO
][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=284f7bcf-4956-40c2-9df5-de8cac60]
Failure in thread: Thread [id=135,
[jira] [Updated] (IGNITE-14868) Failed to get jCache proxy of already started cache within transaction while handling thin client request.
[
https://issues.apache.org/jira/browse/IGNITE-14868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-14868:
-
Description:
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example.Assert that cache context exists.
# Get cache instance by name inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs)
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
Actually, PME finished at this time and I'd expect that the cache 's context
should be already created
{code}
[2021-06-10 10:39:34,072][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish proxy
initialization, cacheName=tx_cache,
localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
[2021-06-10 10:39:34,073][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
Completed partition exchange
[2021-06-10 10:39:34,075][INFO
][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=284f7bcf-4956-40c2-9df5-de8cac60]
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
{code}
was:
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example.Assert that cache context exists.
# Get cache instance by name inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
Actually, PME finished at this time and I'd expect that the cache 's context
should be already created
{code}
[2021-06-10 10:39:34,072][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish proxy
initialization, cacheName=tx_cache,
localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
[2021-06-10 10:39:34,073][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
Completed partition exchange
[2021-06-10 10:39:34,075][INFO
][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=284f7bcf-4956-40c2-9df5-de8cac60]
Failure in
[jira] [Updated] (IGNITE-14868) Failed to get jCache proxy of already started cache within transaction while handling thin client request.
[
https://issues.apache.org/jira/browse/IGNITE-14868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-14868:
-
Description:
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example.Assert that cache context exists.
# Get cache instance by name inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
Actually, PME finished at this time and I'd expect that the cache 's context
should be already created
{code}
[2021-06-10 10:39:34,072][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish proxy
initialization, cacheName=tx_cache,
localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
[2021-06-10 10:39:34,073][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
Completed partition exchange
[2021-06-10 10:39:34,075][INFO
][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=284f7bcf-4956-40c2-9df5-de8cac60]
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
{code}
was:
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example.Assert that cache context exists.
# Get cache instance by name inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs)
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
Actually, PME finished at this time and I'd expect that the cache 's context
should be already created
{code}
[2021-06-10 10:39:34,072][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish proxy
initialization, cacheName=tx_cache,
localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
[2021-06-10 10:39:34,073][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
Completed partition exchange
[2021-06-10 10:39:34,075][INFO
][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=284f7bcf-4956-40c2-9df5-de8cac60]
Failure in
[jira] [Updated] (IGNITE-14868) Failed to get jCache proxy of already started cache within transaction while handling thin client request.
[
https://issues.apache.org/jira/browse/IGNITE-14868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-14868:
-
Attachment: StartTxOnDifferentNodeTest.java
> Failed to get jCache proxy of already started cache within transaction while
> handling thin client request.
> --
>
> Key: IGNITE-14868
> URL: https://issues.apache.org/jira/browse/IGNITE-14868
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ivan Daschinsky
>Priority: Major
> Attachments: StartTxOnDifferentNodeTest.java
>
>
> Description of attached reproducer.
> # Start 2 server nodes
> # Start cache on the first server node (simulate processing of thin client
> request)
> # Start tx on the second server node after starting cache on the first node
> returns (using {{CyclicBarrier}} for example. Get cache instance by name
> inside tx block using
> {{org.apache.ignite.Ignite#cache}} (That is the way the
> {{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
> works
> # Repeat until failure occurs
> {code}
> Failure in thread: Thread [id=135, name=tx-thread-2]
> class org.apache.ignite.IgniteException: Cannot start/stop cache within lock
> or transaction [cacheNames=tx_cache, operation=dynamicStartCache]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
> at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
> {code}
> Actually, PME finished at this time and I'd expect that the cache 's context
> should be already created
> {code}
> [2021-06-10 10:39:34,072][INFO
> ][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish
> proxy initialization, cacheName=tx_cache,
> localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
> [2021-06-10 10:39:34,073][INFO
> ][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
> Completed partition exchange
> [2021-06-10 10:39:34,075][INFO
> ][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
> node=284f7bcf-4956-40c2-9df5-de8cac60]
> Failure in thread: Thread [id=135, name=tx-thread-2]
> class org.apache.ignite.IgniteException: Cannot start/stop cache within lock
> or transaction [cacheNames=tx_cache, operation=dynamicStartCache]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14868) Failed to get jCache proxy of already started cache within transaction while handling thin client request.
[
https://issues.apache.org/jira/browse/IGNITE-14868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-14868:
-
Attachment: (was: StartTxOnDifferentNodeTest.java)
> Failed to get jCache proxy of already started cache within transaction while
> handling thin client request.
> --
>
> Key: IGNITE-14868
> URL: https://issues.apache.org/jira/browse/IGNITE-14868
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ivan Daschinsky
>Priority: Major
> Attachments: StartTxOnDifferentNodeTest.java
>
>
> Description of attached reproducer.
> # Start 2 server nodes
> # Start cache on the first server node (simulate processing of thin client
> request)
> # Start tx on the second server node after starting cache on the first node
> returns (using {{CyclicBarrier}} for example. Get cache instance by name
> inside tx block using
> {{org.apache.ignite.Ignite#cache}} (That is the way the
> {{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
> works
> # Repeat until failure occurs
> {code}
> Failure in thread: Thread [id=135, name=tx-thread-2]
> class org.apache.ignite.IgniteException: Cannot start/stop cache within lock
> or transaction [cacheNames=tx_cache, operation=dynamicStartCache]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
> at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
> {code}
> Actually, PME finished at this time and I'd expect that the cache 's context
> should be already created
> {code}
> [2021-06-10 10:39:34,072][INFO
> ][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish
> proxy initialization, cacheName=tx_cache,
> localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
> [2021-06-10 10:39:34,073][INFO
> ][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
> Completed partition exchange
> [2021-06-10 10:39:34,075][INFO
> ][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
> node=284f7bcf-4956-40c2-9df5-de8cac60]
> Failure in thread: Thread [id=135, name=tx-thread-2]
> class org.apache.ignite.IgniteException: Cannot start/stop cache within lock
> or transaction [cacheNames=tx_cache, operation=dynamicStartCache]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14869) CorruptedTreeException while reactivate and restart cluster under load.
Maksim Timonin created IGNITE-14869: --- Summary: CorruptedTreeException while reactivate and restart cluster under load. Key: IGNITE-14869 URL: https://issues.apache.org/jira/browse/IGNITE-14869 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Assignee: Maksim Timonin Reproducer from user list: http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashed-with-CorruptedTreeException-tt36173.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14868) Failed to get jCache proxy of already started cache within transaction while handling thin client request.
[
https://issues.apache.org/jira/browse/IGNITE-14868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-14868:
-
Description:
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example. Get cache instance by name
inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
Actually, PME finished at this time and I'd expect that the cache 's context
should be already created
{code}
[2021-06-10 10:39:34,072][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridCacheProcessor] Finish proxy
initialization, cacheName=tx_cache,
localNodeId=4cce5a9d-c6a8-44df-936d-f902d411
[2021-06-10 10:39:34,073][INFO
][sys-#99%cache.StartTxOnDifferentNodeTest1%][GridDhtPartitionsExchangeFuture]
Completed partition exchange
[2021-06-10 10:39:34,075][INFO
][exchange-worker-#98%cache.StartTxOnDifferentNodeTest1%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=2, minorTopVer=4], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=284f7bcf-4956-40c2-9df5-de8cac60]
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
{code}
was:
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example. Get cache instance by name
inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
> Failed to get jCache proxy of already started cache within transaction while
> handling thin client request.
> --
>
> Key: IGNITE-14868
> URL: https://issues.apache.org/jira/browse/IGNITE-14868
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ivan Daschinsky
>Priority: Major
> Attachments: StartTxOnDifferentNodeTest.java
>
>
> Description of attached reproducer.
> # Start 2 server nodes
> # Start cache on the first server node (simulate processing of thin client
> request)
> # Start tx on the second server node after starting cache on the first node
> returns (using {{CyclicBarrier}} for example. Get cache
[jira] [Updated] (IGNITE-14868) Failed to get jCache proxy of already started cache within transaction while handling thin client request.
[
https://issues.apache.org/jira/browse/IGNITE-14868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-14868:
-
Attachment: StartTxOnDifferentNodeTest.java
> Failed to get jCache proxy of already started cache within transaction while
> handling thin client request.
> --
>
> Key: IGNITE-14868
> URL: https://issues.apache.org/jira/browse/IGNITE-14868
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ivan Daschinsky
>Priority: Major
> Attachments: StartTxOnDifferentNodeTest.java
>
>
> Description of attached reproducer.
> # Start 2 server nodes
> # Start cache on the first server node (simulate processing of thin client
> request)
> # Start tx on the second server node after starting cache on the first node
> returns (using {{CyclicBarrier}} for example. Get cache instance by name
> inside tx block using
> {{org.apache.ignite.Ignite#cache}} (That is the way the
> {{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
> works
> # Repeat until failure occurs
> {code}
> Failure in thread: Thread [id=135, name=tx-thread-2]
> class org.apache.ignite.IgniteException: Cannot start/stop cache within lock
> or transaction [cacheNames=tx_cache, operation=dynamicStartCache]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
> at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14868) Failed to get jCache proxy of already started cache within transaction while handling thin client request.
Ivan Daschinsky created IGNITE-14868:
Summary: Failed to get jCache proxy of already started cache
within transaction while handling thin client request.
Key: IGNITE-14868
URL: https://issues.apache.org/jira/browse/IGNITE-14868
Project: Ignite
Issue Type: Bug
Affects Versions: 2.10
Reporter: Ivan Daschinsky
Description of attached reproducer.
# Start 2 server nodes
# Start cache on the first server node (simulate processing of thin client
request)
# Start tx on the second server node after starting cache on the first node
returns (using {{CyclicBarrier}} for example. Get cache instance by name
inside tx block using
{{org.apache.ignite.Ignite#cache}} (That is the way the
{{org.apache.ignite.internal.processors.platform.client.ClientRequestHandler}}
works
# Repeat until failure occurs
{code}
Failure in thread: Thread [id=135, name=tx-thread-2]
class org.apache.ignite.IgniteException: Cannot start/stop cache within lock or
transaction [cacheNames=tx_cache, operation=dynamicStartCache]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.checkEmptyTransactions(IgniteTxManager.java:2982)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3487)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4517)
at org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:3194)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
