[jira] [Commented] (IGNITE-9878) Failed to start near cache after second call of getOrCreateCache
[
https://issues.apache.org/jira/browse/IGNITE-9878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845423#comment-16845423
]
Roman Guseinov commented on IGNITE-9878:
[~vkulichenko], yes, it throws on the second invocation.
> Failed to start near cache after second call of getOrCreateCache
>
>
> Key: IGNITE-9878
> URL: https://issues.apache.org/jira/browse/IGNITE-9878
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Attachments: NearCacheIssueReproducer.java, NearCacheTest.java
>
>
> Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
> NearCacheConfiguration nearCfg)` lead the following exception:
> {code:java}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to start near cache (local node is an affinity node for cache):
> ignite-test-near-rep
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2995)
> at
> org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testRepeatedGetOrCreateCache(NearCacheIssueReproducer.java:24)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> near cache (local node is an affinity node for cache): ignite-test-near-rep
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:5235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3621)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3560)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2983)
> ... 23 more
> {code}
> Also, if a cache is specified in the IgniteConfiguration,
> `Ignite#getOrCreateNearCache` will fail with the following exception:
> {code:java}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to start near cache (a cache with the same name without near cache is
> already started)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3072)
> at
> org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testGetOrCreateNearCache(NearCacheIssueReproducer.java:32)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> near cache (a cache with the same name without near cache is already started)
> at
> org.apache.ignite.internal.IgniteKernal.checkNearCacheStarted(IgniteKernal.java:3085)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3067)
> ... 23 more
> {code}
> The test is attached [^NearCacheIssueReproducer.java]. The workaround is to
> put near cache config into cache configuration
> `CacheConfiguration.setNearConfiguration`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9878) Failed to start near cache after second call of getOrCreateCache
[
https://issues.apache.org/jira/browse/IGNITE-9878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844456#comment-16844456
]
Roman Guseinov commented on IGNITE-9878:
[~vkulichenko], thanks for your comment.
I believe it should work like `IgniteCache
getOrCreateCache(CacheConfiguration cacheCfg)`. You can call this method
with the same cacheCfg multiple times without any errors.
If you try to do the same with `IgniteCache
getOrCreateCache(CacheConfiguration cacheCfg, NearCacheConfiguration nearCfg)` the first call will be successful, but the second one will fail.
Does it look correct to you? Why Ignite should throw an exception instead of
returning the same results (like for the first call)?
> Failed to start near cache after second call of getOrCreateCache
>
>
> Key: IGNITE-9878
> URL: https://issues.apache.org/jira/browse/IGNITE-9878
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Attachments: NearCacheIssueReproducer.java, NearCacheTest.java
>
>
> Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
> NearCacheConfiguration nearCfg)` lead the following exception:
> {code:java}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to start near cache (local node is an affinity node for cache):
> ignite-test-near-rep
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2995)
> at
> org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testRepeatedGetOrCreateCache(NearCacheIssueReproducer.java:24)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> near cache (local node is an affinity node for cache): ignite-test-near-rep
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:5235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3621)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3560)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2983)
> ... 23 more
> {code}
> Also, if a cache is specified in the IgniteConfiguration,
> `Ignite#getOrCreateNearCache` will fail with the following exception:
> {code:java}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to start near cache (a cache with the same name without near cache is
> already started)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3072)
> at
> org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testGetOrCreateNearCache(NearCacheIssueReproducer.java:32)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> near cache (a cache with the same name without near cache is already started)
> at
> org.apache.ignite.internal.IgniteKernal.checkNearCacheStarted(IgniteKernal.java:3085)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3067)
> ... 23 more
> {code}
> The test is attached [^NearCacheIssueReproducer.java]. The workaround is to
> put near cache config into cache configuration
> `CacheConfiguration.setNearConfiguration`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9878) Failed to start near cache after second call of getOrCreateCache
[
https://issues.apache.org/jira/browse/IGNITE-9878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-9878:
---
Attachment: NearCacheIssueReproducer.java
> Failed to start near cache after second call of getOrCreateCache
>
>
> Key: IGNITE-9878
> URL: https://issues.apache.org/jira/browse/IGNITE-9878
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Attachments: NearCacheIssueReproducer.java
>
>
> Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
> NearCacheConfiguration nearCfg)` lead the following exception:
> {code:java}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to start near cache (local node is an affinity node for cache):
> ignite-test-near-rep
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2995)
> at
> org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testRepeatedGetOrCreateCache(NearCacheIssueReproducer.java:24)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> near cache (local node is an affinity node for cache): ignite-test-near-rep
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:5235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3621)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3560)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2983)
> ... 23 more
> {code}
> Also, if a cache is specified in the IgniteConfiguration,
> `Ignite#getOrCreateNearCache` will fail with the following exception:
> {code:java}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to start near cache (a cache with the same name without near cache is
> already started)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3072)
> at
> org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testGetOrCreateNearCache(NearCacheIssueReproducer.java:32)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> near cache (a cache with the same name without near cache is already started)
> at
> org.apache.ignite.internal.IgniteKernal.checkNearCacheStarted(IgniteKernal.java:3085)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3067)
> ... 23 more
> {code}
> The test is attached [^NearCacheIssueReproducer.java]. The workaround is to
> put near cache config into cache configuration
> `CacheConfiguration.setNearConfiguration`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9878) Failed to start near cache after second call of getOrCreateCache
[
https://issues.apache.org/jira/browse/IGNITE-9878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-9878:
---
Description:
Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
NearCacheConfiguration nearCfg)` lead the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (local node is an affinity node for cache):
ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2995)
at
org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testRepeatedGetOrCreateCache(NearCacheIssueReproducer.java:24)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start near
cache (local node is an affinity node for cache): ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:5235)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3621)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3560)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2983)
... 23 more
{code}
Also, if a cache is specified in the IgniteConfiguration,
`Ignite#getOrCreateNearCache` will fail with the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (a cache with the same name without near cache is
already started)
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3072)
at
org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testGetOrCreateNearCache(NearCacheIssueReproducer.java:32)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start near
cache (a cache with the same name without near cache is already started)
at
org.apache.ignite.internal.IgniteKernal.checkNearCacheStarted(IgniteKernal.java:3085)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3067)
... 23 more
{code}
The test is attached [^NearCacheIssueReproducer.java]. The workaround is to
put near cache config into cache configuration
`CacheConfiguration.setNearConfiguration`.
was:
Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
NearCacheConfiguration nearCfg)` lead the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (local node is an affinity node for cache):
ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2995)
at
org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testRepeatedGetOrCreateCache(NearCacheIssueReproducer.java:24)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start near
cache (local node is an affinity node for cache): ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:5235)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3621)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3560)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2983)
... 23 more
{code}
Also, if a cache is specified in the IgniteConfiguration,
`Ignite#getOrCreateNearCache` will fail with the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (a cache with the same name without near cache is
already started)
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3072)
at
org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testGetOrCreateNearCache(NearCacheIssueReproducer.java:32)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start near
cache (a cache with the same name without near cache is already started)
at
org.apache.ignite.internal.IgniteKernal.checkNearCacheStarted(IgniteKernal.java:3085)
[jira] [Updated] (IGNITE-9878) Failed to start near cache after second call of getOrCreateCache
[
https://issues.apache.org/jira/browse/IGNITE-9878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-9878:
---
Attachment: (was: NearCacheIssueReproducer.java)
> Failed to start near cache after second call of getOrCreateCache
>
>
> Key: IGNITE-9878
> URL: https://issues.apache.org/jira/browse/IGNITE-9878
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
>
> Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
> NearCacheConfiguration nearCfg)` lead the following exception:
> {code:java}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to start near cache (local node is an affinity node for cache):
> ignite-test-near-rep
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2995)
> at
> org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testRepeatedGetOrCreateCache(NearCacheIssueReproducer.java:24)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> near cache (local node is an affinity node for cache): ignite-test-near-rep
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:5235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3621)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3560)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2983)
> ... 23 more
> {code}
> Also, if a cache is specified in the IgniteConfiguration,
> `Ignite#getOrCreateNearCache` will fail with the following exception:
> {code:java}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to start near cache (a cache with the same name without near cache is
> already started)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3072)
> at
> org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testGetOrCreateNearCache(NearCacheIssueReproducer.java:32)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> near cache (a cache with the same name without near cache is already started)
> at
> org.apache.ignite.internal.IgniteKernal.checkNearCacheStarted(IgniteKernal.java:3085)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3067)
> ... 23 more
> {code}
> The test is attached [^NearCacheIssueReproducer.java]. The workaround is to
> put near cache config into cache configuration
> `CacheConfiguration.setNearConfiguration`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9878) Failed to start near cache after second call of getOrCreateCache
[
https://issues.apache.org/jira/browse/IGNITE-9878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-9878:
---
Description:
Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
NearCacheConfiguration nearCfg)` lead the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (local node is an affinity node for cache):
ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1300)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2872)
at
org.apache.ignite.examples.NearCacheIssueReproducer.testIgniteNearCacheReplicated(NearCacheIssueReproducer.java:29)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start near
cache (local node is an affinity node for cache): ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:4302)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2877)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2816)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2860)
... 23 more
{code}
Also, if a cache is specified in the IgniteConfiguration,
`Ignite#getOrCreateNearCache` will fail with the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (a cache with the same name without near cache is
already started)
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3072)
at
org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testGetOrCreateNearCache(NearCacheIssueReproducer.java:32)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start near
cache (a cache with the same name without near cache is already started)
at
org.apache.ignite.internal.IgniteKernal.checkNearCacheStarted(IgniteKernal.java:3085)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3067)
... 23 more
{code}
The test is attached [^NearCacheIssueReproducer.java]. The workaround is to
put near cache config into cache configuration
`CacheConfiguration.setNearConfiguration`.
was:
Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
NearCacheConfiguration nearCfg)` lead the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (local node is an affinity node for cache):
ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridC
[jira] [Updated] (IGNITE-9878) Failed to start near cache after second call of getOrCreateCache
[
https://issues.apache.org/jira/browse/IGNITE-9878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-9878:
---
Description:
Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
NearCacheConfiguration nearCfg)` lead the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (local node is an affinity node for cache):
ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2995)
at
org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testRepeatedGetOrCreateCache(NearCacheIssueReproducer.java:24)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start near
cache (local node is an affinity node for cache): ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:5235)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3621)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:3560)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2983)
... 23 more
{code}
Also, if a cache is specified in the IgniteConfiguration,
`Ignite#getOrCreateNearCache` will fail with the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (a cache with the same name without near cache is
already started)
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1305)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3072)
at
org.apache.ignite.reproducers.cache.NearCacheIssueReproducer.testGetOrCreateNearCache(NearCacheIssueReproducer.java:32)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start near
cache (a cache with the same name without near cache is already started)
at
org.apache.ignite.internal.IgniteKernal.checkNearCacheStarted(IgniteKernal.java:3085)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateNearCache(IgniteKernal.java:3067)
... 23 more
{code}
The test is attached [^NearCacheIssueReproducer.java]. The workaround is to
put near cache config into cache configuration
`CacheConfiguration.setNearConfiguration`.
was:
Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
NearCacheConfiguration nearCfg)` lead the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (local node is an affinity node for cache):
ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1300)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2872)
at
org.apache.ignite.examples.NearCacheIssueReproducer.testIgniteNearCacheReplicated(NearCacheIssueReproducer.java:29)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at
[jira] [Created] (IGNITE-11660) Add more tests into DmlStatementsProcessorTest
Roman Guseinov created IGNITE-11660: --- Summary: Add more tests into DmlStatementsProcessorTest Key: IGNITE-11660 URL: https://issues.apache.org/jira/browse/IGNITE-11660 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 2.7 Reporter: Roman Guseinov Assignee: Roman Guseinov Add tests to check new versions are compatible with the old ones in both directions: forward and backward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11653) Remove warnings which appear during CPP compiling
[
https://issues.apache.org/jira/browse/IGNITE-11653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-11653:
Attachment: CPPWarnings.log
> Remove warnings which appear during CPP compiling
> -
>
> Key: IGNITE-11653
> URL: https://issues.apache.org/jira/browse/IGNITE-11653
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Priority: Minor
> Attachments: CPPWarnings.log
>
>
> There is two types of warnings:
>
> {code:java}
> src/impl/binary/binary_utils.cpp:92:41: warning: comparison between signed
> and unsigned integer expressions [-Wsign-compare]
> ../common/include/ignite/common/shared_state.h:343:67: warning: 'auto_ptr' is
> deprecated (declared at /usr/include/c++/4.8.2/backward/auto_ptr.h:87)
> [-Wdeprecated-declarations]
> {code}
> The full log is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11653) Remove warnings which appear during CPP compiling
Roman Guseinov created IGNITE-11653:
---
Summary: Remove warnings which appear during CPP compiling
Key: IGNITE-11653
URL: https://issues.apache.org/jira/browse/IGNITE-11653
Project: Ignite
Issue Type: Improvement
Components: platforms
Affects Versions: 2.7
Reporter: Roman Guseinov
Attachments: CPPWarnings.log
There is two types of warnings:
{code:java}
src/impl/binary/binary_utils.cpp:92:41: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
../common/include/ignite/common/shared_state.h:343:67: warning: 'auto_ptr' is
deprecated (declared at /usr/include/c++/4.8.2/backward/auto_ptr.h:87)
[-Wdeprecated-declarations]
{code}
The full log is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11653) Remove warnings which appear during CPP compiling
[
https://issues.apache.org/jira/browse/IGNITE-11653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-11653:
Description:
There are two types of warnings:
{code:java}
src/impl/binary/binary_utils.cpp:92:41: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
../common/include/ignite/common/shared_state.h:343:67: warning: 'auto_ptr' is
deprecated (declared at /usr/include/c++/4.8.2/backward/auto_ptr.h:87)
[-Wdeprecated-declarations]
{code}
The full log is attached.
was:
There is two types of warnings:
{code:java}
src/impl/binary/binary_utils.cpp:92:41: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
../common/include/ignite/common/shared_state.h:343:67: warning: 'auto_ptr' is
deprecated (declared at /usr/include/c++/4.8.2/backward/auto_ptr.h:87)
[-Wdeprecated-declarations]
{code}
The full log is attached.
> Remove warnings which appear during CPP compiling
> -
>
> Key: IGNITE-11653
> URL: https://issues.apache.org/jira/browse/IGNITE-11653
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Priority: Minor
> Attachments: CPPWarnings.log
>
>
> There are two types of warnings:
>
> {code:java}
> src/impl/binary/binary_utils.cpp:92:41: warning: comparison between signed
> and unsigned integer expressions [-Wsign-compare]
> ../common/include/ignite/common/shared_state.h:343:67: warning: 'auto_ptr' is
> deprecated (declared at /usr/include/c++/4.8.2/backward/auto_ptr.h:87)
> [-Wdeprecated-declarations]
> {code}
> The full log is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11634) SQL delete query failed to deserialize entryModifier
[
https://issues.apache.org/jira/browse/IGNITE-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803741#comment-16803741
]
Roman Guseinov commented on IGNITE-11634:
-
[~vozerov] , thank you!
> SQL delete query failed to deserialize entryModifier
>
>
> Key: IGNITE-11634
> URL: https://issues.apache.org/jira/browse/IGNITE-11634
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Here is a stack trace
> {code:java}
> Exception in thread "main" javax.cache.CacheException: Failed to deserialize
> object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:635)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:574)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:356)
> at
> org.gridgain.reproducers.sql.JavaSqlClient.deleteRow(JavaSqlClient.java:42)
> at org.gridgain.reproducers.sql.JavaSqlClient.run(JavaSqlClient.java:33)
> at
> org.gridgain.reproducers.sql.JavaSqlClient.main(JavaSqlClient.java:28)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:686)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.processDmlSelectResult(DmlStatementsProcessor.java:587)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:539)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:171)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:345)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1753)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1718)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2007)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2002)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2550)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:623)
> ... 5 more
> Caused by: java.sql.SQLException: Failed to deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.processPage(DmlBatchSender.java:225)
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.sendBatch(DmlBatchSender.java:184)
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.flush(DmlBatchSender.java:135)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:668)
> ... 17 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10045)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMessage.unmarshalCollection(GridCacheMessage.java:650)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicFullUpdateRequest.finishUnmarshal(GridNearAtomicFullUpdateRequest.java:405)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1609)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java
[jira] [Commented] (IGNITE-11634) SQL delete query failed to deserialize entryModifier
[
https://issues.apache.org/jira/browse/IGNITE-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802626#comment-16802626
]
Roman Guseinov commented on IGNITE-11634:
-
Javadoc issue is related to another commit :
{code:java}
[10:54:26] : [Step 2/2] 1 warning
[10:54:26]W: [Step 2/2] [WARNING] Javadoc Warnings
[10:54:26]W: [Step 2/2] [WARNING]
/data/teamcity/work/c182b70f2dfa6507/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/IgniteCacheDatabaseSharedManager.java:382:
warning - @Deprecated is an unknown tag -- same as a known tag except for case.
{code}
> SQL delete query failed to deserialize entryModifier
>
>
> Key: IGNITE-11634
> URL: https://issues.apache.org/jira/browse/IGNITE-11634
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Here is a stack trace
> {code:java}
> Exception in thread "main" javax.cache.CacheException: Failed to deserialize
> object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:635)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:574)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:356)
> at
> org.gridgain.reproducers.sql.JavaSqlClient.deleteRow(JavaSqlClient.java:42)
> at org.gridgain.reproducers.sql.JavaSqlClient.run(JavaSqlClient.java:33)
> at
> org.gridgain.reproducers.sql.JavaSqlClient.main(JavaSqlClient.java:28)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:686)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.processDmlSelectResult(DmlStatementsProcessor.java:587)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:539)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:171)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:345)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1753)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1718)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2007)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2002)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2550)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:623)
> ... 5 more
> Caused by: java.sql.SQLException: Failed to deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.processPage(DmlBatchSender.java:225)
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.sendBatch(DmlBatchSender.java:184)
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.flush(DmlBatchSender.java:135)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:668)
> ... 17 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10045)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMessage.unmarshalCollection(GridCacheMessage.java:650)
> at
> org.apache.
[jira] [Updated] (IGNITE-11634) SQL delete query failed to deserialize entryModifier
[
https://issues.apache.org/jira/browse/IGNITE-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-11634:
Summary: SQL delete query failed to deserialize entryModifier (was: SQL
delete query failed to deserialize
DmlStatementsProcessor$ModifyingEntryProcessor)
> SQL delete query failed to deserialize entryModifier
>
>
> Key: IGNITE-11634
> URL: https://issues.apache.org/jira/browse/IGNITE-11634
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
>
> Here is a stack trace
> {code:java}
> Exception in thread "main" javax.cache.CacheException: Failed to deserialize
> object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:635)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:574)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:356)
> at
> org.gridgain.reproducers.sql.JavaSqlClient.deleteRow(JavaSqlClient.java:42)
> at org.gridgain.reproducers.sql.JavaSqlClient.run(JavaSqlClient.java:33)
> at
> org.gridgain.reproducers.sql.JavaSqlClient.main(JavaSqlClient.java:28)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:686)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.processDmlSelectResult(DmlStatementsProcessor.java:587)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:539)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:171)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:345)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1753)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1718)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2007)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2002)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2550)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:623)
> ... 5 more
> Caused by: java.sql.SQLException: Failed to deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.processPage(DmlBatchSender.java:225)
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.sendBatch(DmlBatchSender.java:184)
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.flush(DmlBatchSender.java:135)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:668)
> ... 17 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10045)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMessage.unmarshalCollection(GridCacheMessage.java:650)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicFullUpdateRequest.finishUnmarshal(GridNearAtomicFullUpdateRequest.java:405)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1609)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:5
[jira] [Created] (IGNITE-11634) SQL delete query failed to deserialize DmlStatementsProcessor$ModifyingEntryProcessor
Roman Guseinov created IGNITE-11634:
---
Summary: SQL delete query failed to deserialize
DmlStatementsProcessor$ModifyingEntryProcessor
Key: IGNITE-11634
URL: https://issues.apache.org/jira/browse/IGNITE-11634
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.7
Reporter: Roman Guseinov
Assignee: Roman Guseinov
Here is a stack trace
{code:java}
Exception in thread "main" javax.cache.CacheException: Failed to deserialize
object
[typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:635)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:574)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:356)
at
org.gridgain.reproducers.sql.JavaSqlClient.deleteRow(JavaSqlClient.java:42)
at org.gridgain.reproducers.sql.JavaSqlClient.run(JavaSqlClient.java:33)
at
org.gridgain.reproducers.sql.JavaSqlClient.main(JavaSqlClient.java:28)
Caused by: class
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
deserialize object
[typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
at
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:686)
at
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.processDmlSelectResult(DmlStatementsProcessor.java:587)
at
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:539)
at
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:171)
at
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:345)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1753)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1718)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2007)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2002)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2550)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2016)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:623)
... 5 more
Caused by: java.sql.SQLException: Failed to deserialize object
[typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
at
org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.processPage(DmlBatchSender.java:225)
at
org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.sendBatch(DmlBatchSender.java:184)
at
org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.flush(DmlBatchSender.java:135)
at
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:668)
... 17 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
deserialize object
[typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10045)
at
org.apache.ignite.internal.processors.cache.GridCacheMessage.unmarshalCollection(GridCacheMessage.java:650)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicFullUpdateRequest.finishUnmarshal(GridNearAtomicFullUpdateRequest.java:405)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1609)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:586)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
at
org.apache.ignite.internal.processors.cache.G
[jira] [Created] (IGNITE-11541) Dynamic columns and indexes can be lost after the cluster restart
Roman Guseinov created IGNITE-11541: --- Summary: Dynamic columns and indexes can be lost after the cluster restart Key: IGNITE-11541 URL: https://issues.apache.org/jira/browse/IGNITE-11541 Project: Ignite Issue Type: Bug Components: cache, persistence, sql Affects Versions: 2.7 Reporter: Roman Guseinov Attachments: StaticCacheAndDdlReproducer.java The case is the following: # Run a server node (persistence enabled. static cache configuration with queryEnities). # Add/drop column/index via DDL. # Restart the node with the same configuration. # The changes are lost... It seems the issue is related to merging cache metadata. There are some workarounds: # Remove/comment cache configuration. After the restart, the metadata will be loaded from the persistence store. This will work for a rolling restart. # Make the same changes in the configuration (update queryEntity). It requires the whole cluster restart. Reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6578) Too many diagnostic: Found long running cache future
[ https://issues.apache.org/jira/browse/IGNITE-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777936#comment-16777936 ] Roman Guseinov commented on IGNITE-6578: [~ilyak], thanks. > Too many diagnostic: Found long running cache future > > > Key: IGNITE-6578 > URL: https://issues.apache.org/jira/browse/IGNITE-6578 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.1, 2.7 >Reporter: Alexander Belyak >Assignee: Roman Guseinov >Priority: Major > Fix For: 2.8 > > Attachments: LongRunningCacheFutureReproducer.java > > Time Spent: 3h 40m > Remaining Estimate: 0h > > Get about 100Mb of message: > [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] > Found long running cache future > few equals message per ms! Can loose logs by rotating! Can't read logs > without prefiltering! > Reproducer is attached [^LongRunningCacheFutureReproducer.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6578) Too many diagnostic: Found long running cache future
[ https://issues.apache.org/jira/browse/IGNITE-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1681#comment-1681 ] Roman Guseinov commented on IGNITE-6578: Hi [~ilyak], please take a look at the updated PR. > Too many diagnostic: Found long running cache future > > > Key: IGNITE-6578 > URL: https://issues.apache.org/jira/browse/IGNITE-6578 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.1, 2.7 >Reporter: Alexander Belyak >Assignee: Roman Guseinov >Priority: Major > Attachments: LongRunningCacheFutureReproducer.java > > Time Spent: 1.5h > Remaining Estimate: 0h > > Get about 100Mb of message: > [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] > Found long running cache future > few equals message per ms! Can loose logs by rotating! Can't read logs > without prefiltering! > Reproducer is attached [^LongRunningCacheFutureReproducer.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6578) Too many diagnostic: Found long running cache future
[ https://issues.apache.org/jira/browse/IGNITE-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776857#comment-16776857 ] Roman Guseinov commented on IGNITE-6578: [~ilyak], thank you for the review. I've made the required changes and triggered TC tests one more time. > Too many diagnostic: Found long running cache future > > > Key: IGNITE-6578 > URL: https://issues.apache.org/jira/browse/IGNITE-6578 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.1, 2.7 >Reporter: Alexander Belyak >Assignee: Roman Guseinov >Priority: Major > Attachments: LongRunningCacheFutureReproducer.java > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Get about 100Mb of message: > [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] > Found long running cache future > few equals message per ms! Can loose logs by rotating! Can't read logs > without prefiltering! > Reproducer is attached [^LongRunningCacheFutureReproducer.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6578) Too many diagnostic: Found long running cache future
[ https://issues.apache.org/jira/browse/IGNITE-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775187#comment-16775187 ] Roman Guseinov commented on IGNITE-6578: [~ilyak], could you please review the PR https://github.com/apache/ignite/pull/6168 ? > Too many diagnostic: Found long running cache future > > > Key: IGNITE-6578 > URL: https://issues.apache.org/jira/browse/IGNITE-6578 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.1, 2.7 >Reporter: Alexander Belyak >Assignee: Roman Guseinov >Priority: Major > Attachments: LongRunningCacheFutureReproducer.java > > Time Spent: 10m > Remaining Estimate: 0h > > Get about 100Mb of message: > [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] > Found long running cache future > few equals message per ms! Can loose logs by rotating! Can't read logs > without prefiltering! > Reproducer is attached [^LongRunningCacheFutureReproducer.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6578) Too many diagnostic: Found long running cache future
[ https://issues.apache.org/jira/browse/IGNITE-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-6578: --- Description: Get about 100Mb of message: [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] Found long running cache future few equals message per ms! Can loose logs by rotating! Can't read logs without prefiltering! Reproducer is attached [^LongRunningCacheFutureReproducer.java] was: Get about 100Mb of message: [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] Found long running cache future few equals message per ms! Can loose logs by rotating! Can't read logs without prefiltering! > Too many diagnostic: Found long running cache future > > > Key: IGNITE-6578 > URL: https://issues.apache.org/jira/browse/IGNITE-6578 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.1, 2.7 >Reporter: Alexander Belyak >Assignee: Roman Guseinov >Priority: Major > Attachments: LongRunningCacheFutureReproducer.java > > > Get about 100Mb of message: > [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] > Found long running cache future > few equals message per ms! Can loose logs by rotating! Can't read logs > without prefiltering! > Reproducer is attached [^LongRunningCacheFutureReproducer.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6578) Too many diagnostic: Found long running cache future
[ https://issues.apache.org/jira/browse/IGNITE-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-6578: --- Priority: Major (was: Critical) > Too many diagnostic: Found long running cache future > > > Key: IGNITE-6578 > URL: https://issues.apache.org/jira/browse/IGNITE-6578 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.1, 2.7 >Reporter: Alexander Belyak >Priority: Major > Attachments: LongRunningCacheFutureReproducer.java > > > Get about 100Mb of message: > [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] > Found long running cache future > few equals message per ms! Can loose logs by rotating! Can't read logs > without prefiltering! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6578) Too many diagnostic: Found long running cache future
[ https://issues.apache.org/jira/browse/IGNITE-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-6578: --- Affects Version/s: 2.7 > Too many diagnostic: Found long running cache future > > > Key: IGNITE-6578 > URL: https://issues.apache.org/jira/browse/IGNITE-6578 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.1, 2.7 >Reporter: Alexander Belyak >Priority: Critical > Attachments: LongRunningCacheFutureReproducer.java > > > Get about 100Mb of message: > [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] > Found long running cache future > few equals message per ms! Can loose logs by rotating! Can't read logs > without prefiltering! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6578) Too many diagnostic: Found long running cache future
[ https://issues.apache.org/jira/browse/IGNITE-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov reassigned IGNITE-6578: -- Assignee: Roman Guseinov > Too many diagnostic: Found long running cache future > > > Key: IGNITE-6578 > URL: https://issues.apache.org/jira/browse/IGNITE-6578 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.1, 2.7 >Reporter: Alexander Belyak >Assignee: Roman Guseinov >Priority: Major > Attachments: LongRunningCacheFutureReproducer.java > > > Get about 100Mb of message: > [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] > Found long running cache future > few equals message per ms! Can loose logs by rotating! Can't read logs > without prefiltering! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6578) Too many diagnostic: Found long running cache future
[ https://issues.apache.org/jira/browse/IGNITE-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-6578: --- Attachment: LongRunningCacheFutureReproducer.java > Too many diagnostic: Found long running cache future > > > Key: IGNITE-6578 > URL: https://issues.apache.org/jira/browse/IGNITE-6578 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.1 >Reporter: Alexander Belyak >Priority: Critical > Attachments: LongRunningCacheFutureReproducer.java > > > Get about 100Mb of message: > [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] > Found long running cache future > few equals message per ms! Can loose logs by rotating! Can't read logs > without prefiltering! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7309) Sutable exception should be return as job results when node is about to stop.
[
https://issues.apache.org/jira/browse/IGNITE-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757889#comment-16757889
]
Roman Guseinov commented on IGNITE-7309:
[~ilyak], thank you!
> Sutable exception should be return as job results when node is about to stop.
> -
>
> Key: IGNITE-7309
> URL: https://issues.apache.org/jira/browse/IGNITE-7309
> Project: Ignite
> Issue Type: Bug
> Components: compute, general
>Reporter: Andrew Mashenkov
>Assignee: Roman Guseinov
>Priority: Minor
> Labels: newbie, pull-request-available
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> User job can fails with confusing exception when server node is stopping and
> going to leave the grid.
> We should suppress InterruptedException. If node is stopping then user should
> see NodeStoppingException.
> {code:java}
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to serialize
> job response [nodeId=02e1588
> c-53eb-454a-99a1-48ac6cb33667, ses=GridJobSessionImpl
> [ses=GridTaskSessionImpl
> ..
> org.apache.ignite.IgniteCheckedException: Failed to register class.
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9929)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:819)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:760)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:619)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1899)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1519)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1147)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:119)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1087)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to register
> class.
> at
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:778)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:751)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:621)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:164)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:239)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9923)
> ... 14 common frames omitted
> Caused by: org.apache.ignite.internal.IgniteInterruptedCheckedException: null
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.tryGetAndPut(GridDhtAtomicCache.java:724)
> at
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:169)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:168)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:166)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.computeIfAbsent(MarshallerContextAdapter.java:224)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:164
[jira] [Commented] (IGNITE-7309) Sutable exception should be return as job results when node is about to stop.
[
https://issues.apache.org/jira/browse/IGNITE-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754801#comment-16754801
]
Roman Guseinov commented on IGNITE-7309:
[~ilyak], sure )
> Sutable exception should be return as job results when node is about to stop.
> -
>
> Key: IGNITE-7309
> URL: https://issues.apache.org/jira/browse/IGNITE-7309
> Project: Ignite
> Issue Type: Bug
> Components: compute, general
>Reporter: Andrew Mashenkov
>Assignee: Roman Guseinov
>Priority: Minor
> Labels: newbie, pull-request-available
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> User job can fails with confusing exception when server node is stopping and
> going to leave the grid.
> We should suppress InterruptedException. If node is stopping then user should
> see NodeStoppingException.
> {code:java}
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to serialize
> job response [nodeId=02e1588
> c-53eb-454a-99a1-48ac6cb33667, ses=GridJobSessionImpl
> [ses=GridTaskSessionImpl
> ..
> org.apache.ignite.IgniteCheckedException: Failed to register class.
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9929)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:819)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:760)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:619)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1899)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1519)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1147)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:119)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1087)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to register
> class.
> at
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:778)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:751)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:621)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:164)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:239)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9923)
> ... 14 common frames omitted
> Caused by: org.apache.ignite.internal.IgniteInterruptedCheckedException: null
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.tryGetAndPut(GridDhtAtomicCache.java:724)
> at
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:169)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:168)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:166)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.computeIfAbsent(MarshallerContextAdapter.java:224)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:164)
>
[jira] [Commented] (IGNITE-7309) Sutable exception should be return as job results when node is about to stop.
[
https://issues.apache.org/jira/browse/IGNITE-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754731#comment-16754731
]
Roman Guseinov commented on IGNITE-7309:
[~ilyak], thank you for the review. I agree we can simplify if condition. I
created a test before, but [~amashenkov] asked me to remove it arguing this is
unnecessary for such a fix. If you think we really need it I will restore it.
> Sutable exception should be return as job results when node is about to stop.
> -
>
> Key: IGNITE-7309
> URL: https://issues.apache.org/jira/browse/IGNITE-7309
> Project: Ignite
> Issue Type: Bug
> Components: compute, general
>Reporter: Andrew Mashenkov
>Assignee: Roman Guseinov
>Priority: Minor
> Labels: newbie, pull-request-available
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> User job can fails with confusing exception when server node is stopping and
> going to leave the grid.
> We should suppress InterruptedException. If node is stopping then user should
> see NodeStoppingException.
> {code:java}
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to serialize
> job response [nodeId=02e1588
> c-53eb-454a-99a1-48ac6cb33667, ses=GridJobSessionImpl
> [ses=GridTaskSessionImpl
> ..
> org.apache.ignite.IgniteCheckedException: Failed to register class.
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9929)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:819)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:760)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:619)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1899)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1519)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1147)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:119)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1087)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to register
> class.
> at
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:778)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:751)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:621)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:164)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:239)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9923)
> ... 14 common frames omitted
> Caused by: org.apache.ignite.internal.IgniteInterruptedCheckedException: null
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.tryGetAndPut(GridDhtAtomicCache.java:724)
> at
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:169)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:168)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:166)
> at
>
[jira] [Updated] (IGNITE-10950) Lost backup entries when using spring data and cache store
[
https://issues.apache.org/jira/browse/IGNITE-10950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-10950:
Attachment: SpringRepositoryTest.java
> Lost backup entries when using spring data and cache store
> --
>
> Key: IGNITE-10950
> URL: https://issues.apache.org/jira/browse/IGNITE-10950
> Project: Ignite
> Issue Type: Bug
> Components: cache, spring
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Priority: Major
> Attachments: CacheRepository.java, SpringRepositoryTest.java
>
>
> For example, there are 2 server nodes in the cluster. Also, there is a
> replicated cache with a configured cache store. If we try loading entry
> through {{IgniteRepository#findById}} then it can be fetched from the
> cachestore successfully. But if we check the partitions for that entry we
> will find only one primary and there is no backup in the cluster. The
> reproducer is attached [^SpringRepositoryTest.java] [^CacheRepository.java]
> .
> As a workaround it is possible to use {{IgniteCache#get}} instead of
> {{IgniteRepository#findById}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10950) Lost backup entries when using spring data and cache store
[
https://issues.apache.org/jira/browse/IGNITE-10950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-10950:
Attachment: (was: SpringRepositoryTest.java)
> Lost backup entries when using spring data and cache store
> --
>
> Key: IGNITE-10950
> URL: https://issues.apache.org/jira/browse/IGNITE-10950
> Project: Ignite
> Issue Type: Bug
> Components: cache, spring
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Priority: Major
> Attachments: CacheRepository.java, SpringRepositoryTest.java
>
>
> For example, there are 2 server nodes in the cluster. Also, there is a
> replicated cache with a configured cache store. If we try loading entry
> through {{IgniteRepository#findById}} then it can be fetched from the
> cachestore successfully. But if we check the partitions for that entry we
> will find only one primary and there is no backup in the cluster. The
> reproducer is attached [^SpringRepositoryTest.java] [^CacheRepository.java]
> .
> As a workaround it is possible to use {{IgniteCache#get}} instead of
> {{IgniteRepository#findById}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10950) Lost backup entries when using spring data and cache store
[
https://issues.apache.org/jira/browse/IGNITE-10950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-10950:
Description:
For example, there are 2 server nodes in the cluster. Also, there is a
replicated cache with a configured cache store. If we try loading entry through
{{IgniteRepository#findById}} then it can be fetched from the cachestore
successfully. But if we check the partitions for that entry we will find only
one primary and there is no backup in the cluster. The reproducer is attached
[^SpringRepositoryTest.java] [^CacheRepository.java] .
As a workaround it is possible to use {{IgniteCache#get}} instead of
{{IgniteRepository#findById}}.
was:
For example, there are 2 server nodes in the cluster. Also, there is a
replicated cache with a configured cache store. If we try loading entry through
{{IgniteRepository#findById}} then it can be fetched from the cachestore
successfully. But if we check the partitions for that entry we will find only
one primary and there is no backup in the cluster. The reproducer is attached
[^SpringRepositoryTest.java] [^CacheRepository.java] .
As I workaround it is possible to use {{IgniteCache#get}} instead of
{{IgniteRepository#findById}}.
> Lost backup entries when using spring data and cache store
> --
>
> Key: IGNITE-10950
> URL: https://issues.apache.org/jira/browse/IGNITE-10950
> Project: Ignite
> Issue Type: Bug
> Components: cache, spring
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Priority: Major
> Attachments: CacheRepository.java, SpringRepositoryTest.java
>
>
> For example, there are 2 server nodes in the cluster. Also, there is a
> replicated cache with a configured cache store. If we try loading entry
> through {{IgniteRepository#findById}} then it can be fetched from the
> cachestore successfully. But if we check the partitions for that entry we
> will find only one primary and there is no backup in the cluster. The
> reproducer is attached [^SpringRepositoryTest.java] [^CacheRepository.java]
> .
> As a workaround it is possible to use {{IgniteCache#get}} instead of
> {{IgniteRepository#findById}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10950) Lost backup entries when using spring data and cache store
Roman Guseinov created IGNITE-10950:
---
Summary: Lost backup entries when using spring data and cache store
Key: IGNITE-10950
URL: https://issues.apache.org/jira/browse/IGNITE-10950
Project: Ignite
Issue Type: Bug
Components: cache, spring
Affects Versions: 2.7
Reporter: Roman Guseinov
Attachments: CacheRepository.java, SpringRepositoryTest.java
For example, there are 2 server nodes in the cluster. Also, there is a
replicated cache with a configured cache store. If we try loading entry through
{{IgniteRepository#findById}} then it can be fetched from the cachestore
successfully. But if we check the partitions for that entry we will find only
one primary and there is no backup in the cluster. The reproducer is attached
[^SpringRepositoryTest.java] [^CacheRepository.java] .
As I workaround it is possible to use {{IgniteCache#get}} instead of
{{IgniteRepository#findById}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10924) Invalid message type blocks Communication SPI
Roman Guseinov created IGNITE-10924:
---
Summary: Invalid message type blocks Communication SPI
Key: IGNITE-10924
URL: https://issues.apache.org/jira/browse/IGNITE-10924
Project: Ignite
Issue Type: Bug
Components: messaging
Affects Versions: 2.7
Reporter: Roman Guseinov
Attachments: InvalidMessageTypeTest.java
If node A sends a message with a type which is unknown for node B then node B
will fail to process the message and node A will retry sending that message
infinitely. Communication SPI will be blocked. Also, logs from node B will
contain a lot of error messages like the following:
{code:java}
[2019-01-14
18:00:59,957][ERROR][grid-nio-worker-tcp-comm-0-#25%server%][TcpCommunicationSpi]
Closing NIO session because of unhandled exception.
class org.apache.ignite.internal.util.nio.GridNioException: Invalid message
type: 32767
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2409)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2150)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1791)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteException: Invalid message type: 32767
at
org.apache.ignite.internal.managers.communication.GridIoMessageFactory.create(GridIoMessageFactory.java:1164)
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$6.create(TcpCommunicationSpi.java:2322)
at
org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:81)
at
org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at
org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:133)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at
org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3546)
at
org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
at
org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1300)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2383)
... 4 more
{code}
Reproducer is attached [^InvalidMessageTypeTest.java].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8728) Baselined node rejoining crashes other baseline nodes - Duplicate Key Error
[ https://issues.apache.org/jira/browse/IGNITE-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-8728: --- Description: I have two nodes on which we have 3 tables which are partitioned. Index are also built on these tables. For 24 hours caches work fine. The tables are definitely distributed across both the nodes Node 2 reboots due to some issue - goes out of the baseline - comes back and joins the baseline. Other baseline nodes crash and in the logs we see duplicate Key error [10:38:35,437][INFO][tcp-disco-srvr-#2|#2][TcpDiscoverySpi] TCP discovery accepted incoming connection [rmtAddr=/192.168.1.7, rmtPort=45102] [10:38:35,437][INFO][tcp-disco-srvr-#2|#2][TcpDiscoverySpi] TCP discovery spawning a new thread for connection [rmtAddr=/192.168.1.7, rmtPort=45102] [10:38:35,437][INFO][tcp-disco-sock-reader-#12|#12][TcpDiscoverySpi] Started serving remote node connection [rmtAddr=/192.168.1.7:45102, rmtPort=45102] [10:38:35,451][INFO][tcp-disco-sock-reader-#12|#12][TcpDiscoverySpi] Finished serving remote node connection [rmtAddr=/192.168.1.7:45102, rmtPort=45102 [10:38:35,457][SEVERE][tcp-disco-msg-worker-#3|#3][TcpDiscoverySpi] TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node in order to prevent cluster wide instability. *java.lang.IllegalStateException: Duplicate key* at org.apache.ignite.cache.QueryEntity.checkIndexes(QueryEntity.java:223) at org.apache.ignite.cache.QueryEntity.makePatch(QueryEntity.java:174) at org.apache.ignite.internal.processors.query.QuerySchema.makePatch(QuerySchema.java:114) at org.apache.ignite.internal.processors.cache.DynamicCacheDescriptor.makeSchemaPatch(DynamicCacheDescriptor.java:360) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.validateNode(GridCacheProcessor.java:2536) at org.apache.ignite.internal.managers.GridManagerAdapter$1.validateNode(GridManagerAdapter.java:566) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3629) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2736) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536) at org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) [10:38:35,459][SEVERE][tcp-disco-msg-worker-#3|#3][] Critical system error detected. Will be handled accordingly to configured handler [hnd=class o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Duplicate key]] java.lang.IllegalStateException: Duplicate key at org.apache.ignite.cache.QueryEntity.checkIndexes(QueryEntity.java:223) at org.apache.ignite.cache.QueryEntity.makePatch(QueryEntity.java:174) at org.apache.ignite.internal.processors.query.QuerySchema.makePatch(QuerySchema.java:114) at org.apache.ignite.internal.processors.cache.DynamicCacheDescriptor.makeSchemaPatch(DynamicCacheDescriptor.java:360) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.validateNode(GridCacheProcessor.java:2536) at org.apache.ignite.internal.managers.GridManagerAdapter$1.validateNode(GridManagerAdapter.java:566) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3629) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2736) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536) at org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) [10:38:35,460][SEVERE][tcp-disco-msg-worker-#3|#3][] JVM will be halted immediately due to the failure: [failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Duplicate key]] was: I have two nodes on which we have 3 tables which are partitioned. Index are also built on these tables. For 24 hours caches work fine. The tables are definitely distributed across both the nodes Node 2 reboots due to some issue - goes out of the baseline - comes back and joins the baseline. Other baseline nodes crash and in the logs we see duplicate Key error [10:38:35,437][INFO][tcp-disco-srvr-#2|#2][TcpDiscoverySpi] TCP discovery accepted incoming connection [rmtAddr=/192.168.1.7, rmtPort=45102] [10:38:35,437][INFO][tcp-disco-srvr-#2|#2][TcpDiscoverySpi] TCP discovery spawning a new thread for connection [rmtAddr=/192.168.1.
[jira] [Commented] (IGNITE-9826) Ignite node with TcpDiscoveryS3IpFinder can hang while stopping
[
https://issues.apache.org/jira/browse/IGNITE-9826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718928#comment-16718928
]
Roman Guseinov commented on IGNITE-9826:
[~ilyak] , thank you.
> Ignite node with TcpDiscoveryS3IpFinder can hang while stopping
> ---
>
> Key: IGNITE-9826
> URL: https://issues.apache.org/jira/browse/IGNITE-9826
> Project: Ignite
> Issue Type: Bug
> Components: aws
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.8
>
> Attachments: S3IpFinderReproducer.java
>
>
> Here is a stack trace:
> {code:java}
> [15:46:11,081][SEVERE][tcp-disco-ip-finder-cleaner-#4%node1%][TcpDiscoverySpi]
> Failed to clean IP finder up.
> class org.apache.ignite.spi.IgniteSpiException: Failed to list objects in the
> bucket: rguseinov-ipfinder
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:200)
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.s3.S3IpFinderReproducer$CustomS3IpFinder.getRegisteredAddresses(S3IpFinderReproducer.java:103)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1900)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.cleanIpFinder(ServerImpl.java:1998)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.body(ServerImpl.java:1973)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: com.amazonaws.SdkClientException: Failed to sanitize XML document
> destined for handler class
> com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser$ListBucketHandler
> at
> com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.sanitizeXmlDocument(XmlResponsesSaxParser.java:214)
> at
> com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.parseListBucketObjectsResponse(XmlResponsesSaxParser.java:298)
> at
> com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:70)
> at
> com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:59)
> at
> com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:62)
> at
> com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:31)
> at
> com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:70)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1501)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1222)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1035)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:747)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:721)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:704)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:672)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:654)
> at
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:518)
> at
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4137)
> at
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4079)
> at
> com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:819)
> at
> com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:791)
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:148)
> ... 5 more
> Caused by: com.amazonaws.AbortedException:
> at
> com.amazonaws.internal.SdkFilterInputStream.abortIfNeeded(SdkFilterInputStream.java:51)
> at
> com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:71)
> at
> com.amazonaws.event.ProgressInputStream.read(ProgressInputStream.java:181)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.BufferedReader.read1(BufferedReader.java:210)
> at java.io.BufferedRead
[jira] [Updated] (IGNITE-9826) Ignite node with TcpDiscoveryS3IpFinder can hang while stopping
[
https://issues.apache.org/jira/browse/IGNITE-9826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-9826:
---
Fix Version/s: 2.8
> Ignite node with TcpDiscoveryS3IpFinder can hang while stopping
> ---
>
> Key: IGNITE-9826
> URL: https://issues.apache.org/jira/browse/IGNITE-9826
> Project: Ignite
> Issue Type: Bug
> Components: aws
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.8
>
> Attachments: S3IpFinderReproducer.java
>
>
> Here is a stack trace:
> {code:java}
> [15:46:11,081][SEVERE][tcp-disco-ip-finder-cleaner-#4%node1%][TcpDiscoverySpi]
> Failed to clean IP finder up.
> class org.apache.ignite.spi.IgniteSpiException: Failed to list objects in the
> bucket: rguseinov-ipfinder
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:200)
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.s3.S3IpFinderReproducer$CustomS3IpFinder.getRegisteredAddresses(S3IpFinderReproducer.java:103)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1900)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.cleanIpFinder(ServerImpl.java:1998)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.body(ServerImpl.java:1973)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: com.amazonaws.SdkClientException: Failed to sanitize XML document
> destined for handler class
> com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser$ListBucketHandler
> at
> com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.sanitizeXmlDocument(XmlResponsesSaxParser.java:214)
> at
> com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.parseListBucketObjectsResponse(XmlResponsesSaxParser.java:298)
> at
> com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:70)
> at
> com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:59)
> at
> com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:62)
> at
> com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:31)
> at
> com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:70)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1501)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1222)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1035)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:747)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:721)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:704)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:672)
> at
> com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:654)
> at
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:518)
> at
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4137)
> at
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4079)
> at
> com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:819)
> at
> com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:791)
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:148)
> ... 5 more
> Caused by: com.amazonaws.AbortedException:
> at
> com.amazonaws.internal.SdkFilterInputStream.abortIfNeeded(SdkFilterInputStream.java:51)
> at
> com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:71)
> at
> com.amazonaws.event.ProgressInputStream.read(ProgressInputStream.java:181)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.BufferedReader.read1(BufferedReader.java:210)
> at java.io.BufferedReader.read(BufferedReader.java:286)
> at java.io.Reade
[jira] [Commented] (IGNITE-7993) Striped pool can't be disabled
[
https://issues.apache.org/jira/browse/IGNITE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714518#comment-16714518
]
Roman Guseinov commented on IGNITE-7993:
[~ilyak] , thank you. Here is a link to ticket
https://issues.apache.org/jira/browse/IGNITE-9270 (Design thread per partition
model)
> Striped pool can't be disabled
> --
>
> Key: IGNITE-7993
> URL: https://issues.apache.org/jira/browse/IGNITE-7993
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.8
>
>
> Javadoc for {{IgniteConfiguration#setStripedPoolSize}} states that striped
> pool can be disabled by providing value less or equal than zero:
> {noformat}
> If set to non-positive value then requests get processed in system pool.
> {noformat}
> However, doing that prevents node from startup, it fails with the following
> exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid
> stripedPool thread pool size (must be greater than 0), actual value: 0
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.validateThreadPoolSize(IgnitionEx.java:2061)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7993) Striped pool can't be disabled
[
https://issues.apache.org/jira/browse/IGNITE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712423#comment-16712423
]
Roman Guseinov commented on IGNITE-7993:
Hi [~ilyak] , could you please review the javadoc updates
[https://github.com/apache/ignite/pull/5596]? There is going to be implemented
a strict thread per partition in the nearest future which will make disabling
of striped pool impossible.
Thanks.
> Striped pool can't be disabled
> --
>
> Key: IGNITE-7993
> URL: https://issues.apache.org/jira/browse/IGNITE-7993
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.8
>
>
> Javadoc for {{IgniteConfiguration#setStripedPoolSize}} states that striped
> pool can be disabled by providing value less or equal than zero:
> {noformat}
> If set to non-positive value then requests get processed in system pool.
> {noformat}
> However, doing that prevents node from startup, it fails with the following
> exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid
> stripedPool thread pool size (must be greater than 0), actual value: 0
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.validateThreadPoolSize(IgnitionEx.java:2061)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7309) Sutable exception should be return as job results when node is about to stop.
[
https://issues.apache.org/jira/browse/IGNITE-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712381#comment-16712381
]
Roman Guseinov commented on IGNITE-7309:
Hi [~dpavlov] . Looks like I forgot to change the status of the ticket... PR
conflicts are resolved and TC was rerun. Current status of the ticket is PATCH
AVAILABLE. Please take a look.
Thanks.
> Sutable exception should be return as job results when node is about to stop.
> -
>
> Key: IGNITE-7309
> URL: https://issues.apache.org/jira/browse/IGNITE-7309
> Project: Ignite
> Issue Type: Bug
> Components: compute, general
>Reporter: Andrew Mashenkov
>Assignee: Roman Guseinov
>Priority: Minor
> Labels: newbie, pull-request-available
> Fix For: 2.8
>
>
> User job can fails with confusing exception when server node is stopping and
> going to leave the grid.
> We should suppress InterruptedException. If node is stopping then user should
> see NodeStoppingException.
> {code:java}
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to serialize
> job response [nodeId=02e1588
> c-53eb-454a-99a1-48ac6cb33667, ses=GridJobSessionImpl
> [ses=GridTaskSessionImpl
> ..
> org.apache.ignite.IgniteCheckedException: Failed to register class.
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9929)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:819)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:760)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:619)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1899)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1519)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1147)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:119)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1087)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to register
> class.
> at
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:778)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:751)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:621)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:164)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:239)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9923)
> ... 14 common frames omitted
> Caused by: org.apache.ignite.internal.IgniteInterruptedCheckedException: null
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.tryGetAndPut(GridDhtAtomicCache.java:724)
> at
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:169)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:168)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:166)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.computeIfAbsent(MarshallerContextAdap
[jira] [Updated] (IGNITE-7309) Sutable exception should be return as job results when node is about to stop.
[
https://issues.apache.org/jira/browse/IGNITE-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-7309:
---
Description:
User job can fails with confusing exception when server node is stopping and
going to leave the grid.
We should suppress InterruptedException. If node is stopping then user should
see NodeStoppingException.
{code:java}
[org.apache.ignite.internal.processors.job.GridJobWorker] Failed to serialize
job response [nodeId=02e1588
c-53eb-454a-99a1-48ac6cb33667, ses=GridJobSessionImpl [ses=GridTaskSessionImpl
..
org.apache.ignite.IgniteCheckedException: Failed to register class.
at org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9929)
at
org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:819)
at
org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:760)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:619)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
at
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1899)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1519)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1147)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:119)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1087)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to register
class.
at
org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:778)
at
org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:751)
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:621)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:164)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:239)
at
org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
at org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9923)
... 14 common frames omitted
Caused by: org.apache.ignite.internal.IgniteInterruptedCheckedException: null
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.tryGetAndPut(GridDhtAtomicCache.java:724)
at
org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:169)
at
org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:168)
at
org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:166)
at
org.apache.ignite.internal.MarshallerContextAdapter.computeIfAbsent(MarshallerContextAdapter.java:224)
at
org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:164)
at
org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:775)
... 23 common frames omitted
Caused by: java.lang.InterruptedException: null
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1302)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:161)
... 31 common frames omitted
{code}
was:
User job can fails with confusing exception when server node is stopping and
going to leave the grid.
We should suppress InterruptedException. If node is stopping then user should
see NodeStoppingException.
{code:java}
[org.apache.ignite.internal.processors.job.GridJobWorker] Failed to serialize
job response [nodeId=02e1588
c-53eb-454a-99a1-48ac6cb33667, ses=GridJobSessionImpl
[jira] [Updated] (IGNITE-7309) Sutable exception should be return as job results when node is about to stop.
[
https://issues.apache.org/jira/browse/IGNITE-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-7309:
---
Fix Version/s: 2.8
> Sutable exception should be return as job results when node is about to stop.
> -
>
> Key: IGNITE-7309
> URL: https://issues.apache.org/jira/browse/IGNITE-7309
> Project: Ignite
> Issue Type: Bug
> Components: compute, general
>Reporter: Andrew Mashenkov
>Assignee: Roman Guseinov
>Priority: Minor
> Labels: newbie, pull-request-available
> Fix For: 2.8
>
>
> User job can fails with confusing exception when server node is stopping and
> going to leave the grid.
> We should suppress InterruptedException. If node is stopping then user should
> see NodeStoppingException.
> {code:java}
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to serialize
> job response [nodeId=02e1588
> c-53eb-454a-99a1-48ac6cb33667, ses=GridJobSessionImpl
> [ses=GridTaskSessionImpl
> ..
> org.apache.ignite.IgniteCheckedException: Failed to register class.
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9929)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:819)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:760)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:619)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1899)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1519)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1147)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:119)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1087)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to register
> class.
> at
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:778)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:751)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:621)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:164)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:239)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9923)
> ... 14 common frames omitted
> Caused by: org.apache.ignite.internal.IgniteInterruptedCheckedException: null
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.tryGetAndPut(GridDhtAtomicCache.java:724)
> at
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:169)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:168)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:166)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.computeIfAbsent(MarshallerContextAdapter.java:224)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:164)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:775
[jira] [Assigned] (IGNITE-10502) Add a danger block into transactions documentation
[ https://issues.apache.org/jira/browse/IGNITE-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov reassigned IGNITE-10502: --- Assignee: Roman Guseinov > Add a danger block into transactions documentation > -- > > Key: IGNITE-10502 > URL: https://issues.apache.org/jira/browse/IGNITE-10502 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.6 >Reporter: Roman Guseinov >Assignee: Roman Guseinov >Priority: Major > Labels: documentation > > Currently, we can not safely use caches with CacheStore and caches without > this one inside the same transaction. Those types of caches have different > recovery methods and some topology changes can lead inconsistent data: > [https://issues.apache.org/jira/browse/IGNITE-10452|https://issues.apache.org/jira/browse/IGNITE-10452] > It should be mentioned in the documentation to avoid confusing the users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10502) Add a danger block into transactions documentation
[ https://issues.apache.org/jira/browse/IGNITE-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov reassigned IGNITE-10502: --- Assignee: Artem Budnikov (was: Roman Guseinov) > Add a danger block into transactions documentation > -- > > Key: IGNITE-10502 > URL: https://issues.apache.org/jira/browse/IGNITE-10502 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.6 >Reporter: Roman Guseinov >Assignee: Artem Budnikov >Priority: Major > Labels: documentation > > Currently, we can not safely use caches with CacheStore and caches without > this one inside the same transaction. Those types of caches have different > recovery methods and some topology changes can lead inconsistent data: > [https://issues.apache.org/jira/browse/IGNITE-10452|https://issues.apache.org/jira/browse/IGNITE-10452] > It should be mentioned in the documentation to avoid confusing the users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10502) Add a danger block into transactions documentation
Roman Guseinov created IGNITE-10502: --- Summary: Add a danger block into transactions documentation Key: IGNITE-10502 URL: https://issues.apache.org/jira/browse/IGNITE-10502 Project: Ignite Issue Type: Bug Components: documentation Affects Versions: 2.6 Reporter: Roman Guseinov Currently, we can not safely use caches with CacheStore and caches without this one inside the same transaction. Those types of caches have different recovery methods and some topology changes can lead inconsistent data: [https://issues.apache.org/jira/browse/IGNITE-10452|https://issues.apache.org/jira/browse/IGNITE-10452] It should be mentioned in the documentation to avoid confusing the users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10354) Failing client node due to not receiving metrics updates
[
https://issues.apache.org/jira/browse/IGNITE-10354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703138#comment-16703138
]
Roman Guseinov commented on IGNITE-10354:
-
[~ilyak], thank you for the review. I've made requested changes. Do I need to
rerun any tests?
> Failing client node due to not receiving metrics updates
>
>
> Key: IGNITE-10354
> URL: https://issues.apache.org/jira/browse/IGNITE-10354
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Attachments: ClientDisconnectedTest.java
>
>
> In some cases after the coordinator change, the client node can be failed
> before it can establish a connection to another server from the cluster.
> {code:java}
> [2018-11-21 12:21:45,769][WARN
> ][tcp-disco-msg-worker-#15%server-b%][TestTcpDiscoverySpi] Failing client
> node due to not receiving metrics updates from client node within
> 'IgniteConfiguration.clientFailureDetectionTimeout' (consider increasing
> configuration property) [timeout=1, node=TcpDiscoveryNode
> [id=dc739711-f685-45e8-9017-1f91b1d86c8c, addrs=[0:0:0:0:0:0:0:1, 10.0.75.1,
> 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=[/0:0:0:0:0:0:0:1:0,
> LAPTOP-6FN8RAOS/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0,
> /192.168.1.51:0], discPort=0, order=2, intOrder=2,
> lastExchangeTime=1542774105666, loc=false, ver=2.4.0#20180830-sha1:345c0a7c,
> isClient=true]]
> [2018-11-21 12:21:45,791][INFO
> ][tcp-client-disco-msg-worker-#10%client%][TestTcpDiscoverySpi] Client node
> disconnected from cluster, will try to reconnect with new id
> [newId=46812956-2fc4-4b74-9909-d523a547ba0e,
> prevId=dc739711-f685-45e8-9017-1f91b1d86c8c, locNode=TcpDiscoveryNode
> [id=dc739711-f685-45e8-9017-1f91b1d86c8c, addrs=[0:0:0:0:0:0:0:1, 10.0.75.1,
> 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=[/0:0:0:0:0:0:0:1:0,
> LAPTOP-6FN8RAOS/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0,
> /192.168.1.51:0], discPort=0, order=2, intOrder=0,
> lastExchangeTime=1542774104031, loc=true, ver=2.4.0#20180830-sha1:345c0a7c,
> isClient=true]]
> {code}
> It looks like a race condition.
> Steps to reproduce:
> 1. Start server A.
> 2. Start client.
> 3. Start server B.
> 4. Stop server A.
> If add Thread.sleep(1) between (3) and (4) then the client node won't be
> disconnected from the cluster.
> Reproducer is attached [^ClientDisconnectedTest.java].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10452) Inconsistent state of caches if a node stops in the process of running transactions
Roman Guseinov created IGNITE-10452: --- Summary: Inconsistent state of caches if a node stops in the process of running transactions Key: IGNITE-10452 URL: https://issues.apache.org/jira/browse/IGNITE-10452 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.6 Reporter: Roman Guseinov Attachments: NonAcidTxReproducer.java It seems it happens if several caches are used in a transaction. And there are some caches with enabled CacheStore and other ones with disabled. If all caches have CacheStore (or no one has) then the issue doesn't occur. Reproducer is attached (tested on master branch). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10354) Failing client node due to not receiving metrics updates
[
https://issues.apache.org/jira/browse/IGNITE-10354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701293#comment-16701293
]
Roman Guseinov commented on IGNITE-10354:
-
`[Inspections] Core` shows the error `Redundant suppression` in
GridTcpCommunicationSpiRecoverySelfTest:109. This class wasn't touched by
current PR.
> Failing client node due to not receiving metrics updates
>
>
> Key: IGNITE-10354
> URL: https://issues.apache.org/jira/browse/IGNITE-10354
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Attachments: ClientDisconnectedTest.java
>
>
> In some cases after the coordinator change, the client node can be failed
> before it can establish a connection to another server from the cluster.
> {code:java}
> [2018-11-21 12:21:45,769][WARN
> ][tcp-disco-msg-worker-#15%server-b%][TestTcpDiscoverySpi] Failing client
> node due to not receiving metrics updates from client node within
> 'IgniteConfiguration.clientFailureDetectionTimeout' (consider increasing
> configuration property) [timeout=1, node=TcpDiscoveryNode
> [id=dc739711-f685-45e8-9017-1f91b1d86c8c, addrs=[0:0:0:0:0:0:0:1, 10.0.75.1,
> 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=[/0:0:0:0:0:0:0:1:0,
> LAPTOP-6FN8RAOS/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0,
> /192.168.1.51:0], discPort=0, order=2, intOrder=2,
> lastExchangeTime=1542774105666, loc=false, ver=2.4.0#20180830-sha1:345c0a7c,
> isClient=true]]
> [2018-11-21 12:21:45,791][INFO
> ][tcp-client-disco-msg-worker-#10%client%][TestTcpDiscoverySpi] Client node
> disconnected from cluster, will try to reconnect with new id
> [newId=46812956-2fc4-4b74-9909-d523a547ba0e,
> prevId=dc739711-f685-45e8-9017-1f91b1d86c8c, locNode=TcpDiscoveryNode
> [id=dc739711-f685-45e8-9017-1f91b1d86c8c, addrs=[0:0:0:0:0:0:0:1, 10.0.75.1,
> 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=[/0:0:0:0:0:0:0:1:0,
> LAPTOP-6FN8RAOS/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0,
> /192.168.1.51:0], discPort=0, order=2, intOrder=0,
> lastExchangeTime=1542774104031, loc=true, ver=2.4.0#20180830-sha1:345c0a7c,
> isClient=true]]
> {code}
> It looks like a race condition.
> Steps to reproduce:
> 1. Start server A.
> 2. Start client.
> 3. Start server B.
> 4. Stop server A.
> If add Thread.sleep(1) between (3) and (4) then the client node won't be
> disconnected from the cluster.
> Reproducer is attached [^ClientDisconnectedTest.java].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10354) Failing client node due to not receiving metrics updates
[
https://issues.apache.org/jira/browse/IGNITE-10354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov reassigned IGNITE-10354:
---
Assignee: Roman Guseinov
> Failing client node due to not receiving metrics updates
>
>
> Key: IGNITE-10354
> URL: https://issues.apache.org/jira/browse/IGNITE-10354
> Project: Ignite
> Issue Type: Bug
> Components: clients
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Attachments: ClientDisconnectedTest.java
>
>
> In some cases after the coordinator change, the client node can be failed
> before it can establish a connection to another server from the cluster.
> {code:java}
> [2018-11-21 12:21:45,769][WARN
> ][tcp-disco-msg-worker-#15%server-b%][TestTcpDiscoverySpi] Failing client
> node due to not receiving metrics updates from client node within
> 'IgniteConfiguration.clientFailureDetectionTimeout' (consider increasing
> configuration property) [timeout=1, node=TcpDiscoveryNode
> [id=dc739711-f685-45e8-9017-1f91b1d86c8c, addrs=[0:0:0:0:0:0:0:1, 10.0.75.1,
> 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=[/0:0:0:0:0:0:0:1:0,
> LAPTOP-6FN8RAOS/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0,
> /192.168.1.51:0], discPort=0, order=2, intOrder=2,
> lastExchangeTime=1542774105666, loc=false, ver=2.4.0#20180830-sha1:345c0a7c,
> isClient=true]]
> [2018-11-21 12:21:45,791][INFO
> ][tcp-client-disco-msg-worker-#10%client%][TestTcpDiscoverySpi] Client node
> disconnected from cluster, will try to reconnect with new id
> [newId=46812956-2fc4-4b74-9909-d523a547ba0e,
> prevId=dc739711-f685-45e8-9017-1f91b1d86c8c, locNode=TcpDiscoveryNode
> [id=dc739711-f685-45e8-9017-1f91b1d86c8c, addrs=[0:0:0:0:0:0:0:1, 10.0.75.1,
> 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=[/0:0:0:0:0:0:0:1:0,
> LAPTOP-6FN8RAOS/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0,
> /192.168.1.51:0], discPort=0, order=2, intOrder=0,
> lastExchangeTime=1542774104031, loc=true, ver=2.4.0#20180830-sha1:345c0a7c,
> isClient=true]]
> {code}
> It looks like a race condition.
> Steps to reproduce:
> 1. Start server A.
> 2. Start client.
> 3. Start server B.
> 4. Stop server A.
> If add Thread.sleep(1) between (3) and (4) then the client node won't be
> disconnected from the cluster.
> Reproducer is attached [^ClientDisconnectedTest.java].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10354) Failing client node due to not receiving metrics updates
Roman Guseinov created IGNITE-10354:
---
Summary: Failing client node due to not receiving metrics updates
Key: IGNITE-10354
URL: https://issues.apache.org/jira/browse/IGNITE-10354
Project: Ignite
Issue Type: Bug
Components: clients
Affects Versions: 2.6
Reporter: Roman Guseinov
Attachments: ClientDisconnectedTest.java
In some cases after the coordinator change, the client node can be failed
before it can establish a connection to another server from the cluster.
{code:java}
[2018-11-21 12:21:45,769][WARN
][tcp-disco-msg-worker-#15%server-b%][TestTcpDiscoverySpi] Failing client node
due to not receiving metrics updates from client node within
'IgniteConfiguration.clientFailureDetectionTimeout' (consider increasing
configuration property) [timeout=1, node=TcpDiscoveryNode
[id=dc739711-f685-45e8-9017-1f91b1d86c8c, addrs=[0:0:0:0:0:0:0:1, 10.0.75.1,
127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=[/0:0:0:0:0:0:0:1:0,
LAPTOP-6FN8RAOS/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0, /192.168.1.51:0],
discPort=0, order=2, intOrder=2, lastExchangeTime=1542774105666, loc=false,
ver=2.4.0#20180830-sha1:345c0a7c, isClient=true]]
[2018-11-21 12:21:45,791][INFO
][tcp-client-disco-msg-worker-#10%client%][TestTcpDiscoverySpi] Client node
disconnected from cluster, will try to reconnect with new id
[newId=46812956-2fc4-4b74-9909-d523a547ba0e,
prevId=dc739711-f685-45e8-9017-1f91b1d86c8c, locNode=TcpDiscoveryNode
[id=dc739711-f685-45e8-9017-1f91b1d86c8c, addrs=[0:0:0:0:0:0:0:1, 10.0.75.1,
127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=[/0:0:0:0:0:0:0:1:0,
LAPTOP-6FN8RAOS/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0, /192.168.1.51:0],
discPort=0, order=2, intOrder=0, lastExchangeTime=1542774104031, loc=true,
ver=2.4.0#20180830-sha1:345c0a7c, isClient=true]]
{code}
It looks like a race condition.
Steps to reproduce:
1. Start server A.
2. Start client.
3. Start server B.
4. Stop server A.
If add Thread.sleep(1) between (3) and (4) then the client node won't be
disconnected from the cluster.
Reproducer is attached [^ClientDisconnectedTest.java].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9937) Primary response error info can be lost due to unwrapping a key
[
https://issues.apache.org/jira/browse/IGNITE-9937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694144#comment-16694144
]
Roman Guseinov commented on IGNITE-9937:
[~agoncharuk], thank you.
> Primary response error info can be lost due to unwrapping a key
> ---
>
> Key: IGNITE-9937
> URL: https://issues.apache.org/jira/browse/IGNITE-9937
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.8
>
>
> It can happen when we use SQL DDL to create a table or some dummy values for
> QueryEntity.keyType. Without using Cache API (only SQL), key and value should
> not be deserialized/unwrapped.
> If primary update error happens onPrimaryError call may try to unwrap keys,
> get ClassNotFoundException and hide the original error.
> Here is a stack trace example:
> {code:java}
> Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:
> TestTableKey
>at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:706)
>at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1755)
>at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
>at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:797)
>at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:177)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:67)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:404)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onPrimaryResponse(GridNearAtomicUpdateFuture.java:416)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:390)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1832)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1633)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:812)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:664)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$25.apply(GridDhtAtomicCache.java:1067)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$25.apply(GridDhtAtomicCache.java:1065)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:761)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1065)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAllConflictAsync(GridDhtAtomicCache.java:687)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAllConflict(GridDhtAtomicCache.java:680)
>at
> org.apache.ignite.internal.processors.dr.IgniteDrDataStreamerCacheUpdater.receive(IgniteDrDataStreamerCacheUpdater.java:97)
>at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
>at
> org.apache.ignite.i
[jira] [Commented] (IGNITE-9937) Primary response error info can be lost due to unwrapping a key
[
https://issues.apache.org/jira/browse/IGNITE-9937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680884#comment-16680884
]
Roman Guseinov commented on IGNITE-9937:
Hi [~ilyak], after adding one more test and updating the fix, I found out that
it's not enough to store keys as binary objects inside
CachePartialUpdateCheckedException. This can lead to failed tests in jcache and
dotnet.
The newest fix resolves the original issue and doesn't affect other use cases.
Could you please take a look again at PR
https://github.com/apache/ignite/pull/5078?
> Primary response error info can be lost due to unwrapping a key
> ---
>
> Key: IGNITE-9937
> URL: https://issues.apache.org/jira/browse/IGNITE-9937
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
>
> It can happen when we use SQL DDL to create a table or some dummy values for
> QueryEntity.keyType. Without using Cache API (only SQL), key and value should
> not be deserialized/unwrapped.
> If primary update error happens onPrimaryError call may try to unwrap keys,
> get ClassNotFoundException and hide the original error.
> Here is a stack trace example:
> {code:java}
> Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:
> TestTableKey
>at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:706)
>at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1755)
>at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
>at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:797)
>at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:177)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:67)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:404)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onPrimaryResponse(GridNearAtomicUpdateFuture.java:416)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:390)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1832)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1633)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:812)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:664)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$25.apply(GridDhtAtomicCache.java:1067)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$25.apply(GridDhtAtomicCache.java:1065)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:761)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1065)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAllConflictAsync(GridDhtAtomicCache.java:687)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomi
[jira] [Commented] (IGNITE-9937) Primary response error info can be lost due to unwrapping a key
[
https://issues.apache.org/jira/browse/IGNITE-9937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669578#comment-16669578
]
Roman Guseinov commented on IGNITE-9937:
Hi [~ilyak], thank you for the review. I've updated the fix based on your
suggestion and added a comment on GitHub. Also, one more test was added since
original fix is not enough if we try to put a batch with the size of more then
1. Could you please take a look?
> Primary response error info can be lost due to unwrapping a key
> ---
>
> Key: IGNITE-9937
> URL: https://issues.apache.org/jira/browse/IGNITE-9937
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
>
> It can happen when we use SQL DDL to create a table or some dummy values for
> QueryEntity.keyType. Without using Cache API (only SQL), key and value should
> not be deserialized/unwrapped.
> If primary update error happens onPrimaryError call may try to unwrap keys,
> get ClassNotFoundException and hide the original error.
> Here is a stack trace example:
> {code:java}
> Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:
> TestTableKey
>at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:706)
>at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1755)
>at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
>at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:797)
>at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:177)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:67)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:404)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onPrimaryResponse(GridNearAtomicUpdateFuture.java:416)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:390)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1832)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1633)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:812)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:664)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$25.apply(GridDhtAtomicCache.java:1067)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$25.apply(GridDhtAtomicCache.java:1065)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:761)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1065)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAllConflictAsync(GridDhtAtomicCache.java:687)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAllConflict(GridDhtAtomicCache.java:680)
>at
> org.apache.ignite.internal.processors.dr.IgniteDrDataStreamerC
[jira] [Created] (IGNITE-9956) Web Agent should handle EOFException in the process of node stopping
Roman Guseinov created IGNITE-9956:
--
Summary: Web Agent should handle EOFException in the process of
node stopping
Key: IGNITE-9956
URL: https://issues.apache.org/jira/browse/IGNITE-9956
Project: Ignite
Issue Type: Bug
Components: UI
Reporter: Roman Guseinov
If web agent is connected to a node which starts stopping we will see the
following message in the agent's logs:
{code:java}
[2018-10-03 12:19:32,672][ERROR][pool-3-thread-48][AbstractListener] Failed to
execute REST command with parameters: {p1=6840C2E6-EE22-4F96-8BC3-35DFD60497CF,
p2=org.gridgain.grid.internal.visor.node.VisorGridGainNodeConfigurationCollectorTask,
p3=java.lang.Void, name=o.a.i.i.v.compute.VisorGatewayTask, cmd=exe}
java.io.IOException: unexpected end of stream on
Connection{datafabric-dev-22.test.com:8080, proxy=DIRECT
hostAddress=datafabric-dev-22.test.com/10.54.1.21:8080 cipherSuite=none
protocol=http/1.1}
at
okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:205)
at
okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:75)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at
okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
at
okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
at
okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:185)
at okhttp3.RealCall.execute(RealCall.java:69)
at
org.apache.ignite.console.agent.rest.RestExecutor.sendRequest(RestExecutor.java:169)
at
org.apache.ignite.console.agent.rest.RestExecutor.sendRequest(RestExecutor.java:184)
at
org.apache.ignite.console.agent.handlers.RestListener.execute(RestListener.java:85)
at
org.apache.ignite.console.agent.handlers.AbstractListener.lambda$call$0(AbstractListener.java:76)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.EOFException: \n not found: limit=0 content=…
at
okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:226)
at
okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:210)
at
okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189)
... 24 more
{code}
It looks like node returns an empty response. Web agent should handle that,
print a more understandable message and start trying to connect to other nodes
immediately.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9937) Primary response error info can be lost due to unwrapping a key
[
https://issues.apache.org/jira/browse/IGNITE-9937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656243#comment-16656243
]
Roman Guseinov commented on IGNITE-9937:
[~vozerov] , do we need any test for this small fix:
https://github.com/gridgain/apache-ignite/commit/1c8f40cba2b1808ddd0a803183c002757c8eae74
?
> Primary response error info can be lost due to unwrapping a key
> ---
>
> Key: IGNITE-9937
> URL: https://issues.apache.org/jira/browse/IGNITE-9937
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
>
> It can happen when we use SQL DDL to create a table or some dummy values for
> QueryEntity.keyType. Without using Cache API (only SQL), key and value should
> not be deserialized/unwrapped.
> If primary update error happens onPrimaryError call may try to unwrap keys,
> get ClassNotFoundException and hide the original error.
> Here is a stack trace example:
> {code:java}
> Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:
> TestTableKey
>at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:706)
>at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1755)
>at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
>at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:797)
>at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:177)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:67)
>at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:404)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onPrimaryResponse(GridNearAtomicUpdateFuture.java:416)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:390)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1832)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1633)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:812)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:664)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$25.apply(GridDhtAtomicCache.java:1067)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$25.apply(GridDhtAtomicCache.java:1065)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:761)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1065)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAllConflictAsync(GridDhtAtomicCache.java:687)
>at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAllConflict(GridDhtAtomicCache.java:680)
>at
> org.apache.ignite.internal.processors.dr.IgniteDrDataStreamerCacheUpdater.receive(IgniteDrDataStreamerCacheUpdater.java:97)
>at
> org.apache.ignite.internal.processors.datastream
[jira] [Created] (IGNITE-9937) Primary response error info can be lost due to unwrapping a key
Roman Guseinov created IGNITE-9937:
--
Summary: Primary response error info can be lost due to unwrapping
a key
Key: IGNITE-9937
URL: https://issues.apache.org/jira/browse/IGNITE-9937
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.6
Reporter: Roman Guseinov
Assignee: Roman Guseinov
It can happen when we use SQL DDL to create a table or some dummy values for
QueryEntity.keyType. Without using Cache API (only SQL), key and value should
not be deserialized/unwrapped.
If primary update error happens onPrimaryError call may try to unwrap keys, get
ClassNotFoundException and hide the original error.
Here is a stack trace example:
{code:java}
Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:
TestTableKey
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:706)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1755)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:797)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
at
org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:177)
at
org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:67)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:404)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onPrimaryResponse(GridNearAtomicUpdateFuture.java:416)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:303)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:300)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:390)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1832)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1633)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:812)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:664)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$25.apply(GridDhtAtomicCache.java:1067)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$25.apply(GridDhtAtomicCache.java:1065)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:761)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1065)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAllConflictAsync(GridDhtAtomicCache.java:687)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAllConflict(GridDhtAtomicCache.java:680)
at
org.apache.ignite.internal.processors.dr.IgniteDrDataStreamerCacheUpdater.receive(IgniteDrDataStreamerCacheUpdater.java:97)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6720)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
... 4 more
Caused by: java.lang.ClassNotFoundException: TestTableKey
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
at java
[jira] [Created] (IGNITE-9878) Failed to start near cache after second call of getOrCreateCache
Roman Guseinov created IGNITE-9878:
--
Summary: Failed to start near cache after second call of
getOrCreateCache
Key: IGNITE-9878
URL: https://issues.apache.org/jira/browse/IGNITE-9878
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.6
Reporter: Roman Guseinov
Assignee: Roman Guseinov
Attachments: NearCacheIssueReproducer.java
Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg,
NearCacheConfiguration nearCfg)` lead the following exception:
{code:java}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to start near cache (local node is an affinity node for cache):
ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1300)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2872)
at
org.apache.ignite.examples.NearCacheIssueReproducer.testIgniteNearCacheReplicated(NearCacheIssueReproducer.java:29)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start near
cache (local node is an affinity node for cache): ignite-test-near-rep
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:4302)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2877)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2816)
at
org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2860)
... 23 more
{code}
The test is attached [^NearCacheIssueReproducer.java]. The workaround is to
put near cache config into cache configuration
`CacheConfiguration.setNearConfiguration`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9826) Ignite node with TcpDiscoveryS3IpFinder can hang while stopping
[
https://issues.apache.org/jira/browse/IGNITE-9826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-9826:
---
Description:
Here is a stack trace:
{code:java}
[15:46:11,081][SEVERE][tcp-disco-ip-finder-cleaner-#4%node1%][TcpDiscoverySpi]
Failed to clean IP finder up.
class org.apache.ignite.spi.IgniteSpiException: Failed to list objects in the
bucket: rguseinov-ipfinder
at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:200)
at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.S3IpFinderReproducer$CustomS3IpFinder.getRegisteredAddresses(S3IpFinderReproducer.java:103)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1900)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.cleanIpFinder(ServerImpl.java:1998)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.body(ServerImpl.java:1973)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: com.amazonaws.SdkClientException: Failed to sanitize XML document
destined for handler class
com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser$ListBucketHandler
at
com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.sanitizeXmlDocument(XmlResponsesSaxParser.java:214)
at
com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.parseListBucketObjectsResponse(XmlResponsesSaxParser.java:298)
at
com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:70)
at
com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:59)
at
com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:62)
at
com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:31)
at
com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:70)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1501)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1222)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1035)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:747)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:721)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:704)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:672)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:654)
at
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:518)
at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4137)
at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4079)
at
com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:819)
at
com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:791)
at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:148)
... 5 more
Caused by: com.amazonaws.AbortedException:
at
com.amazonaws.internal.SdkFilterInputStream.abortIfNeeded(SdkFilterInputStream.java:51)
at
com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:71)
at
com.amazonaws.event.ProgressInputStream.read(ProgressInputStream.java:181)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.read1(BufferedReader.java:210)
at java.io.BufferedReader.read(BufferedReader.java:286)
at java.io.Reader.read(Reader.java:140)
at
com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.sanitizeXmlDocument(XmlResponsesSaxParser.java:186)
... 25 more
{code}
Reproducer is attached [^S3IpFinderReproducer.java] .
was:
Here is stack trace:
{code:java}
[15:46:11,081][SEVERE][tcp-disco-ip-finder-cleaner-#4%node1%][TcpDiscoverySpi]
Failed to clean IP finder up.
class org.apache.ignite.spi.IgniteSpiException: Failed to list objects in the
bucket: rguseinov-ipfinder
at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinde
[jira] [Created] (IGNITE-9826) Ignite node with TcpDiscoveryS3IpFinder can hang while stopping
Roman Guseinov created IGNITE-9826:
--
Summary: Ignite node with TcpDiscoveryS3IpFinder can hang while
stopping
Key: IGNITE-9826
URL: https://issues.apache.org/jira/browse/IGNITE-9826
Project: Ignite
Issue Type: Bug
Components: aws
Affects Versions: 2.6
Reporter: Roman Guseinov
Assignee: Roman Guseinov
Attachments: S3IpFinderReproducer.java
Here is stack trace:
{code:java}
[15:46:11,081][SEVERE][tcp-disco-ip-finder-cleaner-#4%node1%][TcpDiscoverySpi]
Failed to clean IP finder up.
class org.apache.ignite.spi.IgniteSpiException: Failed to list objects in the
bucket: rguseinov-ipfinder
at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:200)
at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.S3IpFinderReproducer$CustomS3IpFinder.getRegisteredAddresses(S3IpFinderReproducer.java:103)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1900)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.cleanIpFinder(ServerImpl.java:1998)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.body(ServerImpl.java:1973)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: com.amazonaws.SdkClientException: Failed to sanitize XML document
destined for handler class
com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser$ListBucketHandler
at
com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.sanitizeXmlDocument(XmlResponsesSaxParser.java:214)
at
com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.parseListBucketObjectsResponse(XmlResponsesSaxParser.java:298)
at
com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:70)
at
com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:59)
at
com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:62)
at
com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:31)
at
com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:70)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1501)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1222)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1035)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:747)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:721)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:704)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:672)
at
com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:654)
at
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:518)
at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4137)
at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4079)
at
com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:819)
at
com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:791)
at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:148)
... 5 more
Caused by: com.amazonaws.AbortedException:
at
com.amazonaws.internal.SdkFilterInputStream.abortIfNeeded(SdkFilterInputStream.java:51)
at
com.amazonaws.internal.SdkFilterInputStream.read(SdkFilterInputStream.java:71)
at
com.amazonaws.event.ProgressInputStream.read(ProgressInputStream.java:181)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.read1(BufferedReader.java:210)
at java.io.BufferedReader.read(BufferedReader.java:286)
at java.io.Reader.read(Reader.java:140)
at
com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.sanitizeXmlDocument(XmlResponsesSaxParser.java:186)
... 25 more
{code}
Reproducer is attached [^S3IpFinderReproducer.java] .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7993) Striped pool can't be disabled
[
https://issues.apache.org/jira/browse/IGNITE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626994#comment-16626994
]
Roman Guseinov commented on IGNITE-7993:
Hi [~NIzhikov] , if this issue is still relevant I will resolve conflicts. Do
you need the fix in 2.7?
> Striped pool can't be disabled
> --
>
> Key: IGNITE-7993
> URL: https://issues.apache.org/jira/browse/IGNITE-7993
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.7
>
>
> Javadoc for {{IgniteConfiguration#setStripedPoolSize}} states that striped
> pool can be disabled by providing value less or equal than zero:
> {noformat}
> If set to non-positive value then requests get processed in system pool.
> {noformat}
> However, doing that prevents node from startup, it fails with the following
> exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid
> stripedPool thread pool size (must be greater than 0), actual value: 0
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.validateThreadPoolSize(IgnitionEx.java:2061)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9555) Web Console can stop due to an unexpected message via web sockets
[
https://issues.apache.org/jira/browse/IGNITE-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-9555:
---
Ignite Flags: (was: Docs Required)
> Web Console can stop due to an unexpected message via web sockets
> -
>
> Key: IGNITE-9555
> URL: https://issues.apache.org/jira/browse/IGNITE-9555
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Roman Guseinov
>Priority: Major
> Attachments: webconsole.log
>
>
> Web Console shows error only if debug messages are enabled `DEBUG=mongodb-*
> ./gridgain-web-console-linux`. Otherwise, it just stops.
> Here is the error message:
> {code:java}
> /snapshot/backend/node_modules/ignite-web-console/app/browsersHandler.js:211
> return cb('Invalid format of message: "node:rest"');
> ^
> TypeError: cb is not a function
> at Socket.module.exports.factory.nodeListeners.sock.on
> (/snapshot/backend/node_modules/ignite-web-console/app/browsersHandler.js:211:32)
> at emitThree (events.js:136:13)
> at Socket.emit (events.js:217:7)
> at
> /snapshot/backend/node_modules/ignite-web-console/node_modules/socket.io/lib/socket.js:503:12
> at _combinedTickCallback (internal/process/next_tick.js:131:7)
> at process._tickCallback (internal/process/next_tick.js:180:9)
> {code}
> The full log is attached: [^webconsole.log].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9555) Web Console can stop due to an unexpected message via web sockets
Roman Guseinov created IGNITE-9555:
--
Summary: Web Console can stop due to an unexpected message via web
sockets
Key: IGNITE-9555
URL: https://issues.apache.org/jira/browse/IGNITE-9555
Project: Ignite
Issue Type: Bug
Components: wizards
Reporter: Roman Guseinov
Attachments: webconsole.log
Web Console shows error only if debug messages are enabled `DEBUG=mongodb-*
./gridgain-web-console-linux`. Otherwise, it just stops.
Here is the error message:
{code:java}
/snapshot/backend/node_modules/ignite-web-console/app/browsersHandler.js:211
return cb('Invalid format of message: "node:rest"');
^
TypeError: cb is not a function
at Socket.module.exports.factory.nodeListeners.sock.on
(/snapshot/backend/node_modules/ignite-web-console/app/browsersHandler.js:211:32)
at emitThree (events.js:136:13)
at Socket.emit (events.js:217:7)
at
/snapshot/backend/node_modules/ignite-web-console/node_modules/socket.io/lib/socket.js:503:12
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
{code}
The full log is attached: [^webconsole.log].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8987) Ignite hangs during getting of atomic structure after autoactivation
[ https://issues.apache.org/jira/browse/IGNITE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603878#comment-16603878 ] Roman Guseinov commented on IGNITE-8987: [~agoncharuk] , thank you. > Ignite hangs during getting of atomic structure after autoactivation > > > Key: IGNITE-8987 > URL: https://issues.apache.org/jira/browse/IGNITE-8987 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Andrey Aleksandrov >Assignee: Roman Guseinov >Priority: Major > Fix For: 2.7 > > Attachments: reproducer.java > > > I investigate the use cases with autoactivation and creating of the > IgniteAtomicSequence. It hangs on awaitInitialization() method in case if it > called after the last node from BLT was started. > Steps to reproduce: > First iteration: > > Do next in one thread: > 1)Start server 1 > 2)Start server 2 > 3)Activate the cluster > 4)Create the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > atomicConfiguration, > 10, > true); > Second iteration: > 1)Start server 1 > 2)Start server 2 (Autoactivation will be started) > 3)Get the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > 10, > true); //could be false because TestName was already created in iteration 1 > In this case, we hang in awaitInitialization() method in > DataStructureProcessor.getAtomic() method. > In case if I added some sleep timeout between step 2 and 3 in the second > iteration then everything was ok. Looks like we have some race here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8987) Ignite hangs during getting of atomic structure after autoactivation
[ https://issues.apache.org/jira/browse/IGNITE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602607#comment-16602607 ] Roman Guseinov commented on IGNITE-8987: [~dpavlov] , could you please review the PR [https://github.com/apache/ignite/pull/4664] ? TC results: [https://ci.ignite.apache.org/viewQueued.html?itemId=1785623] Restarted tests: * PDS (Direct IO) 2 [https://ci.ignite.apache.org/viewLog.html?buildId=1789396] * Run :: .NET [https://ci.ignite.apache.org/viewQueued.html?itemId=1789404] All failed tests seem flaky. Thanks. > Ignite hangs during getting of atomic structure after autoactivation > > > Key: IGNITE-8987 > URL: https://issues.apache.org/jira/browse/IGNITE-8987 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Andrey Aleksandrov >Assignee: Roman Guseinov >Priority: Major > Fix For: 2.7 > > Attachments: reproducer.java > > > I investigate the use cases with autoactivation and creating of the > IgniteAtomicSequence. It hangs on awaitInitialization() method in case if it > called after the last node from BLT was started. > Steps to reproduce: > First iteration: > > Do next in one thread: > 1)Start server 1 > 2)Start server 2 > 3)Activate the cluster > 4)Create the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > atomicConfiguration, > 10, > true); > Second iteration: > 1)Start server 1 > 2)Start server 2 (Autoactivation will be started) > 3)Get the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > 10, > true); //could be false because TestName was already created in iteration 1 > In this case, we hang in awaitInitialization() method in > DataStructureProcessor.getAtomic() method. > In case if I added some sleep timeout between step 2 and 3 in the second > iteration then everything was ok. Looks like we have some race here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8987) Ignite hangs during getting of atomic structure after autoactivation
[ https://issues.apache.org/jira/browse/IGNITE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602604#comment-16602604 ] Roman Guseinov commented on IGNITE-8987: [~ilyak] , thank you for the review. > Ignite hangs during getting of atomic structure after autoactivation > > > Key: IGNITE-8987 > URL: https://issues.apache.org/jira/browse/IGNITE-8987 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Andrey Aleksandrov >Assignee: Roman Guseinov >Priority: Major > Fix For: 2.7 > > Attachments: reproducer.java > > > I investigate the use cases with autoactivation and creating of the > IgniteAtomicSequence. It hangs on awaitInitialization() method in case if it > called after the last node from BLT was started. > Steps to reproduce: > First iteration: > > Do next in one thread: > 1)Start server 1 > 2)Start server 2 > 3)Activate the cluster > 4)Create the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > atomicConfiguration, > 10, > true); > Second iteration: > 1)Start server 1 > 2)Start server 2 (Autoactivation will be started) > 3)Get the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > 10, > true); //could be false because TestName was already created in iteration 1 > In this case, we hang in awaitInitialization() method in > DataStructureProcessor.getAtomic() method. > In case if I added some sleep timeout between step 2 and 3 in the second > iteration then everything was ok. Looks like we have some race here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9367) CPP: ODBC client crashes after executing query with closed connection
[
https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594846#comment-16594846
]
Roman Guseinov commented on IGNITE-9367:
[~isapego] , thank you.
> CPP: ODBC client crashes after executing query with closed connection
> -
>
> Key: IGNITE-9367
> URL: https://issues.apache.org/jira/browse/IGNITE-9367
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
> Environment: Ubuntu 16.04
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Labels: cpp
> Attachments: odbc-crash-reproducer.cpp, server-config.xml
>
>
> This scenario should not lead an application crash. It seems we should throw
> an exception like "Connection is closed" instead.
> Thread dump:
> {code:java}
> Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal :
> SIGSEGV:Segmentation fault)
> ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628
> 0x454264
> ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd
> ignite::odbc::Connection::SyncMessage ignite::odbc::QueryExecuteResponse>() at connection.h:168 0x45c705
> ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217
> 0x45c705
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629
> 0x42d32e
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586
> 0x42d499
> ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1
> ignite::SQLExecDirect() at odbc.cpp:395 0x42614c
> GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a
> QueryData() at odbc-crash-reproducer.cpp:172 0x408af2
> <...more frames...>
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9367) CPP: ODBC client crashes after executing query with closed connection
[
https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594772#comment-16594772
]
Roman Guseinov commented on IGNITE-9367:
[~isapego] , thank you for the review. I've added the new test to MSVC solution.
> CPP: ODBC client crashes after executing query with closed connection
> -
>
> Key: IGNITE-9367
> URL: https://issues.apache.org/jira/browse/IGNITE-9367
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
> Environment: Ubuntu 16.04
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Labels: cpp
> Attachments: odbc-crash-reproducer.cpp, server-config.xml
>
>
> This scenario should not lead an application crash. It seems we should throw
> an exception like "Connection is closed" instead.
> Thread dump:
> {code:java}
> Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal :
> SIGSEGV:Segmentation fault)
> ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628
> 0x454264
> ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd
> ignite::odbc::Connection::SyncMessage ignite::odbc::QueryExecuteResponse>() at connection.h:168 0x45c705
> ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217
> 0x45c705
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629
> 0x42d32e
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586
> 0x42d499
> ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1
> ignite::SQLExecDirect() at odbc.cpp:395 0x42614c
> GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a
> QueryData() at odbc-crash-reproducer.cpp:172 0x408af2
> <...more frames...>
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9367) CPP: ODBC client crashes after executing query with closed connection
[
https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594616#comment-16594616
]
Roman Guseinov commented on IGNITE-9367:
[~isapego] , could you please review the PR
[https://github.com/apache/ignite/pull/4621] ?
TC results are green:
* Platform C++ (Linux)
[https://ci.ignite.apache.org/viewLog.html?buildId=1748145&tab=queuedBuildOverviewTab]
* Platform C++ (Linux Clang)
[https://ci.ignite.apache.org/viewLog.html?buildId=1748143&tab=queuedBuildOverviewTab]
* Platform C++ (Windows x64)
[https://ci.ignite.apache.org/viewLog.html?buildId=1748363&;]
* Platform C++ (Windows x86)
[https://ci.ignite.apache.org/viewLog.html?buildId=1748149&;]
Thanks.
> CPP: ODBC client crashes after executing query with closed connection
> -
>
> Key: IGNITE-9367
> URL: https://issues.apache.org/jira/browse/IGNITE-9367
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
> Environment: Ubuntu 16.04
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Labels: cpp
> Attachments: odbc-crash-reproducer.cpp, server-config.xml
>
>
> This scenario should not lead an application crash. It seems we should throw
> an exception like "Connection is closed" instead.
> Thread dump:
> {code:java}
> Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal :
> SIGSEGV:Segmentation fault)
> ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628
> 0x454264
> ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd
> ignite::odbc::Connection::SyncMessage ignite::odbc::QueryExecuteResponse>() at connection.h:168 0x45c705
> ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217
> 0x45c705
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629
> 0x42d32e
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586
> 0x42d499
> ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1
> ignite::SQLExecDirect() at odbc.cpp:395 0x42614c
> GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a
> QueryData() at odbc-crash-reproducer.cpp:172 0x408af2
> <...more frames...>
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9367) CPP: ODBC client crashes after executing query with closed connection
[
https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594612#comment-16594612
]
Roman Guseinov commented on IGNITE-9367:
[~ilyak] , thank you a lot for the quick response.
> CPP: ODBC client crashes after executing query with closed connection
> -
>
> Key: IGNITE-9367
> URL: https://issues.apache.org/jira/browse/IGNITE-9367
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
> Environment: Ubuntu 16.04
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Labels: cpp
> Attachments: odbc-crash-reproducer.cpp, server-config.xml
>
>
> This scenario should not lead an application crash. It seems we should throw
> an exception like "Connection is closed" instead.
> Thread dump:
> {code:java}
> Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal :
> SIGSEGV:Segmentation fault)
> ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628
> 0x454264
> ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd
> ignite::odbc::Connection::SyncMessage ignite::odbc::QueryExecuteResponse>() at connection.h:168 0x45c705
> ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217
> 0x45c705
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629
> 0x42d32e
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586
> 0x42d499
> ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1
> ignite::SQLExecDirect() at odbc.cpp:395 0x42614c
> GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a
> QueryData() at odbc-crash-reproducer.cpp:172 0x408af2
> <...more frames...>
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9367) CPP: ODBC client crashes after executing query with closed connection
[
https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593511#comment-16593511
]
Roman Guseinov commented on IGNITE-9367:
[~ilyak] , could you please review the PR
[https://github.com/apache/ignite/pull/4621] ?
TC results (Platform C++ (Linux)) are here
[https://ci.ignite.apache.org/viewLog.html?buildId=1743759&tab=queuedBuildOverviewTab]
Thanks.
> CPP: ODBC client crashes after executing query with closed connection
> -
>
> Key: IGNITE-9367
> URL: https://issues.apache.org/jira/browse/IGNITE-9367
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
> Environment: Ubuntu 16.04
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Labels: cpp
> Attachments: odbc-crash-reproducer.cpp, server-config.xml
>
>
> This scenario should not lead an application crash. It seems we should throw
> an exception like "Connection is closed" instead.
> Thread dump:
> {code:java}
> Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal :
> SIGSEGV:Segmentation fault)
> ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628
> 0x454264
> ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd
> ignite::odbc::Connection::SyncMessage ignite::odbc::QueryExecuteResponse>() at connection.h:168 0x45c705
> ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217
> 0x45c705
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629
> 0x42d32e
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586
> 0x42d499
> ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1
> ignite::SQLExecDirect() at odbc.cpp:395 0x42614c
> GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a
> QueryData() at odbc-crash-reproducer.cpp:172 0x408af2
> <...more frames...>
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9367) CPP: ODBC client crashes after executing query with closed connection
Roman Guseinov created IGNITE-9367:
--
Summary: CPP: ODBC client crashes after executing query with
closed connection
Key: IGNITE-9367
URL: https://issues.apache.org/jira/browse/IGNITE-9367
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.6
Environment: Ubuntu 16.04
Reporter: Roman Guseinov
Assignee: Roman Guseinov
Attachments: odbc-crash-reproducer.cpp, server-config.xml
This scenario should not lead an application crash. It seems we should throw an
exception like "Connection is closed" instead.
Thread dump:
{code:java}
Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal :
SIGSEGV:Segmentation fault)
ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628 0x454264
ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd
ignite::odbc::Connection::SyncMessage() at connection.h:168 0x45c705
ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217
0x45c705
ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629
0x42d32e
ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586
0x42d499
ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1
ignite::SQLExecDirect() at odbc.cpp:395 0x42614c
GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a
QueryData() at odbc-crash-reproducer.cpp:172 0x408af2
<...more frames...>
{code}
Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9367) CPP: ODBC client crashes after executing query with closed connection
[
https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-9367:
---
Ignite Flags: (was: Docs Required)
> CPP: ODBC client crashes after executing query with closed connection
> -
>
> Key: IGNITE-9367
> URL: https://issues.apache.org/jira/browse/IGNITE-9367
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
> Environment: Ubuntu 16.04
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Labels: cpp
> Attachments: odbc-crash-reproducer.cpp, server-config.xml
>
>
> This scenario should not lead an application crash. It seems we should throw
> an exception like "Connection is closed" instead.
> Thread dump:
> {code:java}
> Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal :
> SIGSEGV:Segmentation fault)
> ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628
> 0x454264
> ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd
> ignite::odbc::Connection::SyncMessage ignite::odbc::QueryExecuteResponse>() at connection.h:168 0x45c705
> ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217
> 0x45c705
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629
> 0x42d32e
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586
> 0x42d499
> ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1
> ignite::SQLExecDirect() at odbc.cpp:395 0x42614c
> GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a
> QueryData() at odbc-crash-reproducer.cpp:172 0x408af2
> <...more frames...>
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8546) Permission denied while copying OPTION_LIBS on Openshift
[ https://issues.apache.org/jira/browse/IGNITE-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555448#comment-16555448 ] Roman Guseinov commented on IGNITE-8546: [~vveider] , thanks a lot for the review. > Permission denied while copying OPTION_LIBS on Openshift > > > Key: IGNITE-8546 > URL: https://issues.apache.org/jira/browse/IGNITE-8546 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.4, 2.5, 2.6 > Environment: Server https://api.pro-us-east-1.openshift.com:443 > openshift v3.9.14 > kubernetes v1.9.1+a0ce1bc657 >Reporter: Roman Guseinov >Assignee: Roman Guseinov >Priority: Major > Labels: docker > Attachments: Dockerfile > > > The issue happens when we try to deploy `apacheignite/ignite:2.4.0` on > Openshift with specified OPTION_LIBS env variable > "ignite-kubernetes,ignite-rest-http". > There is a workaround how to resolve this issue. Dockerfile is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-8546) Permission denied while copying OPTION_LIBS on Openshift
[ https://issues.apache.org/jira/browse/IGNITE-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-8546: --- Comment: was deleted (was: [~vveider] , could you please review the PR?) > Permission denied while copying OPTION_LIBS on Openshift > > > Key: IGNITE-8546 > URL: https://issues.apache.org/jira/browse/IGNITE-8546 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.4, 2.5, 2.6 > Environment: Server https://api.pro-us-east-1.openshift.com:443 > openshift v3.9.14 > kubernetes v1.9.1+a0ce1bc657 >Reporter: Roman Guseinov >Assignee: Roman Guseinov >Priority: Major > Labels: docker > Attachments: Dockerfile > > > The issue happens when we try to deploy `apacheignite/ignite:2.4.0` on > Openshift with specified OPTION_LIBS env variable > "ignite-kubernetes,ignite-rest-http". > There is a workaround how to resolve this issue. Dockerfile is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8546) Permission denied while copying OPTION_LIBS on Openshift
[ https://issues.apache.org/jira/browse/IGNITE-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555447#comment-16555447 ] Roman Guseinov commented on IGNITE-8546: [~vveider] , could you please review the PR? > Permission denied while copying OPTION_LIBS on Openshift > > > Key: IGNITE-8546 > URL: https://issues.apache.org/jira/browse/IGNITE-8546 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.4, 2.5, 2.6 > Environment: Server https://api.pro-us-east-1.openshift.com:443 > openshift v3.9.14 > kubernetes v1.9.1+a0ce1bc657 >Reporter: Roman Guseinov >Assignee: Roman Guseinov >Priority: Major > Labels: docker > Attachments: Dockerfile > > > The issue happens when we try to deploy `apacheignite/ignite:2.4.0` on > Openshift with specified OPTION_LIBS env variable > "ignite-kubernetes,ignite-rest-http". > There is a workaround how to resolve this issue. Dockerfile is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8546) Permission denied while copying OPTION_LIBS on Openshift
[ https://issues.apache.org/jira/browse/IGNITE-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555389#comment-16555389 ] Roman Guseinov commented on IGNITE-8546: The updated Dockerfile was built locally, published on DockerHub `gromtech/ignite:2.6.0` and tested on Openshift and Google Cloud Platform (Kubernetes). > Permission denied while copying OPTION_LIBS on Openshift > > > Key: IGNITE-8546 > URL: https://issues.apache.org/jira/browse/IGNITE-8546 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.4, 2.5, 2.6 > Environment: Server https://api.pro-us-east-1.openshift.com:443 > openshift v3.9.14 > kubernetes v1.9.1+a0ce1bc657 >Reporter: Roman Guseinov >Assignee: Roman Guseinov >Priority: Major > Labels: docker > Attachments: Dockerfile > > > The issue happens when we try to deploy `apacheignite/ignite:2.4.0` on > Openshift with specified OPTION_LIBS env variable > "ignite-kubernetes,ignite-rest-http". > There is a workaround how to resolve this issue. Dockerfile is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8546) Permission denied while copying OPTION_LIBS on Openshift
[ https://issues.apache.org/jira/browse/IGNITE-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-8546: --- Affects Version/s: 2.5 2.6 > Permission denied while copying OPTION_LIBS on Openshift > > > Key: IGNITE-8546 > URL: https://issues.apache.org/jira/browse/IGNITE-8546 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.4, 2.5, 2.6 > Environment: Server https://api.pro-us-east-1.openshift.com:443 > openshift v3.9.14 > kubernetes v1.9.1+a0ce1bc657 >Reporter: Roman Guseinov >Assignee: Roman Guseinov >Priority: Major > Attachments: Dockerfile > > > The issue happens when we try to deploy `apacheignite/ignite:2.4.0` on > Openshift with specified OPTION_LIBS env variable > "ignite-kubernetes,ignite-rest-http". > There is a workaround how to resolve this issue. Dockerfile is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8546) Permission denied while copying OPTION_LIBS on Openshift
[ https://issues.apache.org/jira/browse/IGNITE-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555449#comment-16555449 ] Roman Guseinov edited comment on IGNITE-8546 at 7/25/18 9:42 AM: - [~dpavlov] could you please review PR [https://github.com/apache/ignite/pull/4427] ? I am not sure that we need TC results for these changes. was (Author: guseinov): [~dpavlov] could you please review PR [https://github.com/apache/ignite/pull/4427] I am not sure that we need a TC results for this changes. > Permission denied while copying OPTION_LIBS on Openshift > > > Key: IGNITE-8546 > URL: https://issues.apache.org/jira/browse/IGNITE-8546 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.4, 2.5, 2.6 > Environment: Server https://api.pro-us-east-1.openshift.com:443 > openshift v3.9.14 > kubernetes v1.9.1+a0ce1bc657 >Reporter: Roman Guseinov >Assignee: Roman Guseinov >Priority: Major > Labels: docker > Attachments: Dockerfile > > > The issue happens when we try to deploy `apacheignite/ignite:2.4.0` on > Openshift with specified OPTION_LIBS env variable > "ignite-kubernetes,ignite-rest-http". > There is a workaround how to resolve this issue. Dockerfile is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8546) Permission denied while copying OPTION_LIBS on Openshift
[ https://issues.apache.org/jira/browse/IGNITE-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555449#comment-16555449 ] Roman Guseinov commented on IGNITE-8546: [~dpavlov] could you please review PR [https://github.com/apache/ignite/pull/4427] I am not sure that we need a TC results for this changes. > Permission denied while copying OPTION_LIBS on Openshift > > > Key: IGNITE-8546 > URL: https://issues.apache.org/jira/browse/IGNITE-8546 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.4, 2.5, 2.6 > Environment: Server https://api.pro-us-east-1.openshift.com:443 > openshift v3.9.14 > kubernetes v1.9.1+a0ce1bc657 >Reporter: Roman Guseinov >Assignee: Roman Guseinov >Priority: Major > Labels: docker > Attachments: Dockerfile > > > The issue happens when we try to deploy `apacheignite/ignite:2.4.0` on > Openshift with specified OPTION_LIBS env variable > "ignite-kubernetes,ignite-rest-http". > There is a workaround how to resolve this issue. Dockerfile is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9072) Memory Configuration for client nodes
[ https://issues.apache.org/jira/browse/IGNITE-9072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-9072: --- Issue Type: Improvement (was: Bug) > Memory Configuration for client nodes > - > > Key: IGNITE-9072 > URL: https://issues.apache.org/jira/browse/IGNITE-9072 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.6 >Reporter: Roman Guseinov >Priority: Major > > Some users believe that off-heap region configuration [1] won't be applied on > client nodes because those nodes don't keep data. So, sometimes users just > copy the configuration from server nodes, set clientMode = true and apply to > client node. It can lead to issues like [2]. > I think it makes sense to mention that off-heap region configuration can be > required only for local caches on client nodes. Users should avoid such > configuration on client nodes if they don't use local caches. > [1] [https://apacheignite.readme.io/docs/memory-configuration] > [2] https://issues.apache.org/jira/browse/IGNITE-9071 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9072) Memory Configuration for client nodes
Roman Guseinov created IGNITE-9072: -- Summary: Memory Configuration for client nodes Key: IGNITE-9072 URL: https://issues.apache.org/jira/browse/IGNITE-9072 Project: Ignite Issue Type: Bug Components: documentation Affects Versions: 2.6 Reporter: Roman Guseinov Some users believe that off-heap region configuration [1] won't be applied on client nodes because those nodes don't keep data. So, sometimes users just copy the configuration from server nodes, set clientMode = true and apply to client node. It can lead to issues like [2]. I think it makes sense to mention that off-heap region configuration can be required only for local caches on client nodes. Users should avoid such configuration on client nodes if they don't use local caches. [1] [https://apacheignite.readme.io/docs/memory-configuration] [2] https://issues.apache.org/jira/browse/IGNITE-9071 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9071) Failed to reinitialize local partitions on client node
[
https://issues.apache.org/jira/browse/IGNITE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-9071:
---
Affects Version/s: 2.6
> Failed to reinitialize local partitions on client node
> --
>
> Key: IGNITE-9071
> URL: https://issues.apache.org/jira/browse/IGNITE-9071
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Priority: Minor
> Labels: newbie
> Attachments: Reproducer.java
>
>
> "Failed to reinitialize local partitions" message can confuse users when it
> appears in the client node logs:
>
> {code}
> [2018-07-25
> 12:15:58,717][ERROR][exchange-worker-#80%client-node%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (rebalancing will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2,
> minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=aa407026-3050-4dac-899d-cec951b3c9e5, addrs=ArrayList [10.0.75.1,
> 10.8.10.46, 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=HashSet
> [/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0, /192.168.1.51:0,
> /10.8.10.46:0], discPort=0, order=2, intOrder=0,
> lastExchangeTime=1532492155372, loc=true, ver=2.7.0#19700101-sha1:,
> isClient=true], topVer=2, nodeId8=aa407026, msg=null, type=NODE_JOINED,
> tstamp=1532492158693], nodeId=aa407026, evt=NODE_JOINED]
> java.lang.OutOfMemoryError
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at
> org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1090)
> at
> org.apache.ignite.internal.mem.unsafe.UnsafeMemoryProvider.nextRegion(UnsafeMemoryProvider.java:90)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager$2.nextRegion(IgniteCacheDatabaseSharedManager.java:1026)
> at
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.addSegment(PageMemoryNoStoreImpl.java:628)
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9071) Failed to reinitialize local partitions on client node
Roman Guseinov created IGNITE-9071:
--
Summary: Failed to reinitialize local partitions on client node
Key: IGNITE-9071
URL: https://issues.apache.org/jira/browse/IGNITE-9071
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Roman Guseinov
Attachments: Reproducer.java
"Failed to reinitialize local partitions" message can confuse users when it
appears in the client node logs:
{code}
[2018-07-25
12:15:58,717][ERROR][exchange-worker-#80%client-node%][GridDhtPartitionsExchangeFuture]
Failed to reinitialize local partitions (rebalancing will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2,
minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=aa407026-3050-4dac-899d-cec951b3c9e5, addrs=ArrayList [10.0.75.1,
10.8.10.46, 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=HashSet
[/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0, /192.168.1.51:0, /10.8.10.46:0],
discPort=0, order=2, intOrder=0, lastExchangeTime=1532492155372, loc=true,
ver=2.7.0#19700101-sha1:, isClient=true], topVer=2, nodeId8=aa407026,
msg=null, type=NODE_JOINED, tstamp=1532492158693], nodeId=aa407026,
evt=NODE_JOINED]
java.lang.OutOfMemoryError
at sun.misc.Unsafe.allocateMemory(Native Method)
at
org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1090)
at
org.apache.ignite.internal.mem.unsafe.UnsafeMemoryProvider.nextRegion(UnsafeMemoryProvider.java:90)
at
org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager$2.nextRegion(IgniteCacheDatabaseSharedManager.java:1026)
at
org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.addSegment(PageMemoryNoStoreImpl.java:628)
{code}
Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8923) Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
[
https://issues.apache.org/jira/browse/IGNITE-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov reassigned IGNITE-8923:
--
Assignee: Denis Magda (was: Ilya Murchenko)
> Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
>
>
> Key: IGNITE-8923
> URL: https://issues.apache.org/jira/browse/IGNITE-8923
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Roman Guseinov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.7
>
> Attachments: config.zip, example-kube.xml,
> google_cloud_engine_deployment.zip, yaml.zip
>
>
> We have such documentation for Microsoft Azure
> [https://apacheignite.readme.io/docs/microsoft-azure-deployment]
> It would be great to publish the same for GCE.
> Here are steps which I used to deploy cluster (stateless, stateful) and web
> console:
> {code:java}
> ## Start Ignite Cluster
> 1. Grant cluster-admin role to current google user (to allow create roles):
> $ kubectl create clusterrolebinding myname2-cluster-admin-binding \
> --clusterrole=cluster-admin \
> --user=
> 2. Create service account and grant permissions:
> $ kubectl create -f sa.yaml
> $ kubectl create -f role.yaml
> $ kubectl create -f rolebind.yaml
> 3. Create a grid service:
> $ kubectl create -f service.yaml
> 4. Deploy Ignite Cluster:
> $ kubectl create -f grid.yaml
> ## Enable Ignite Persistence
> 5. Deploy Ignite StatefulSet with enabled Persistence (instead of step 4).
> $ kubectl create -f grid-pds.yaml
> 6. Connect to the Ignite node and activate cluster:
> $ kubectl exec -it ignite-cluster-0 -- /bin/bash
> $ cd /opt/ignite/apache-ignite-*
> $ ./bin/control.sh --activate
> ## Deploy Web Console:
> 7. Create a volume to keep web console data:
> $ kubectl create -f console-volume.yaml
> 8. Create load balancer to expose HTTP port and make web console available by
> service DNS-name (web-console.default.svc.cluster.local) inside Kuberntes
> enviroment:
> $ kubectl create -f console-service.yaml
> 9. Deploy Web Console:
> $ kubectl create -f console.yaml
> 10. Check external IP:
> $ kubectl get service web-console
> 11. Open Web Console in a web browser and Sign Up.
> 12. Move to User Profile page (Settings > Profile) and copy security token.
> 13. Insert security token into web-agent.yaml (TOKENS environment variable).
> 14. Deploy Web Agent:
> $ kubectl create -f web-agent.yaml
> {code}
> YAML and configs are attached.
> Creating a public Docker-image for Web Agent in progress:
> https://issues.apache.org/jira/browse/IGNITE-8526
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9007) cache.invoke() fails because of UnregisteredClassException
Roman Guseinov created IGNITE-9007:
--
Summary: cache.invoke() fails because of
UnregisteredClassException
Key: IGNITE-9007
URL: https://issues.apache.org/jira/browse/IGNITE-9007
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.5
Reporter: Roman Guseinov
Assignee: Mikhail Cherkasov
Attachments: ClientNode.java, CustomEnum.java, CustomObj.java,
Reproducer.java, ServerNode.java
Here is a stack trace:
{code:java}
[2018-07-16 18:07:30,624][ERROR][main][BinaryContext] Failed to serialize
object [typeName=o.a.i.reproducers.fd7776.CustomObj]
class org.apache.ignite.binary.BinaryObjectException: Failed to write field
[name=obj]
at
org.apache.ignite.internal.binary.BinaryFieldAccessor.write(BinaryFieldAccessor.java:159)
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:807)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:216)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:157)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:144)
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:254)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:402)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:386)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:881)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheObject(CacheObjectBinaryProcessorImpl.java:831)
at
org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheObject(GridCacheContext.java:1802)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.runEntryProcessor(GridCacheMapEntry.java:5350)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.call(GridCacheMapEntry.java:4705)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.call(GridCacheMapEntry.java:4515)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:3083)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$6200(BPlusTree.java:2977)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1726)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1610)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1306)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:381)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1761)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2436)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1898)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1740)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1630)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1119)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke0(GridDhtAtomicCache.java:827)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke(GridDhtAtomicCache.java:787)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1417)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCach
[jira] [Commented] (IGNITE-7993) Striped pool can't be disabled
[
https://issues.apache.org/jira/browse/IGNITE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534526#comment-16534526
]
Roman Guseinov commented on IGNITE-7993:
Hi [~yzhdanov] . Thank you for the review. I made the necessary changes and
added tests (DisabledStripedExecutorFailoverTest,
DisabledStripedExecutorFullApiTest).
TC result: https://ci.ignite.apache.org/viewLog.html?buildId=1460792
Please let me know if I need to add more tests.
Thanks.
> Striped pool can't be disabled
> --
>
> Key: IGNITE-7993
> URL: https://issues.apache.org/jira/browse/IGNITE-7993
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.7
>
>
> Javadoc for {{IgniteConfiguration#setStripedPoolSize}} states that striped
> pool can be disabled by providing value less or equal than zero:
> {noformat}
> If set to non-positive value then requests get processed in system pool.
> {noformat}
> However, doing that prevents node from startup, it fails with the following
> exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid
> stripedPool thread pool size (must be greater than 0), actual value: 0
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.validateThreadPoolSize(IgnitionEx.java:2061)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8546) Permission denied while copying OPTION_LIBS on Openshift
[ https://issues.apache.org/jira/browse/IGNITE-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov reassigned IGNITE-8546: -- Assignee: Roman Guseinov > Permission denied while copying OPTION_LIBS on Openshift > > > Key: IGNITE-8546 > URL: https://issues.apache.org/jira/browse/IGNITE-8546 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.4 > Environment: Server https://api.pro-us-east-1.openshift.com:443 > openshift v3.9.14 > kubernetes v1.9.1+a0ce1bc657 >Reporter: Roman Guseinov >Assignee: Roman Guseinov >Priority: Major > Attachments: Dockerfile > > > The issue happens when we try to deploy `apacheignite/ignite:2.4.0` on > Openshift with specified OPTION_LIBS env variable > "ignite-kubernetes,ignite-rest-http". > There is a workaround how to resolve this issue. Dockerfile is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7993) Striped pool can't be disabled
[
https://issues.apache.org/jira/browse/IGNITE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532180#comment-16532180
]
Roman Guseinov commented on IGNITE-7993:
Hi [~yzhdanov] , could you please take a look at the PR
[https://github.com/apache/ignite/pull/4235]
Thanks in advance.
> Striped pool can't be disabled
> --
>
> Key: IGNITE-7993
> URL: https://issues.apache.org/jira/browse/IGNITE-7993
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.7
>
>
> Javadoc for {{IgniteConfiguration#setStripedPoolSize}} states that striped
> pool can be disabled by providing value less or equal than zero:
> {noformat}
> If set to non-positive value then requests get processed in system pool.
> {noformat}
> However, doing that prevents node from startup, it fails with the following
> exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid
> stripedPool thread pool size (must be greater than 0), actual value: 0
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.validateThreadPoolSize(IgnitionEx.java:2061)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8923) Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
Roman Guseinov created IGNITE-8923:
--
Summary: Add step-by-step guide - Google Cloud Engine Deployment
(Kubernetes)
Key: IGNITE-8923
URL: https://issues.apache.org/jira/browse/IGNITE-8923
Project: Ignite
Issue Type: Improvement
Components: documentation
Reporter: Roman Guseinov
Attachments: config.zip, yaml.zip
We have such documentation for Microsoft Azure
[https://apacheignite.readme.io/docs/microsoft-azure-deployment]
It would be great to publish the same for GCE.
Here are steps which I used to deploy cluster (stateless, stateful) and web
console:
{code:java}
## Start Ignite Cluster
1. Grant cluster-admin role to current google user (to allow create roles):
$ kubectl create clusterrolebinding myname2-cluster-admin-binding \
--clusterrole=cluster-admin \
--user=
2. Create service account and grant permissions:
$ kubectl create -f sa.yaml
$ kubectl create -f role.yaml
$ kubectl create -f rolebind.yaml
3. Create a grid service:
$ kubectl create -f service.yaml
4. Deploy Ignite Cluster:
$ kubectl create -f grid.yaml
## Enable Ignite Persistence
5. Deploy Ignite StatefulSet with enabled Persistence (instead of step 4).
$ kubectl create -f grid-pds.yaml
6. Connect to the Ignite node and activate cluster:
$ kubectl exec -it ignite-cluster-0 -- /bin/bash
$ cd /opt/ignite/apache-ignite-*
$ ./bin/control.sh --activate
## Deploy Web Console:
7. Create a volume to keep web console data:
$ kubectl create -f console-volume.yaml
8. Create load balancer to expose HTTP port and make web console available by
service DNS-name (web-console.default.svc.cluster.local) inside Kuberntes
enviroment:
$ kubectl create -f console-service.yaml
9. Deploy Web Console:
$ kubectl create -f console.yaml
10. Check external IP:
$ kubectl get service web-console
11. Open Web Console in a web browser and Sign Up.
12. Move to User Profile page (Settings > Profile) and copy security token.
13. Insert security token into web-agent.yaml (TOKENS environment variable).
14. Deploy Web Agent:
$ kubectl create -f web-agent.yaml
{code}
YAML and configs are attached.
Creating a public Docker-image for Web Agent in progress:
https://issues.apache.org/jira/browse/IGNITE-8526
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7993) Striped pool can't be disabled
[
https://issues.apache.org/jira/browse/IGNITE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526296#comment-16526296
]
Roman Guseinov commented on IGNITE-7993:
[~vkulichenko] , thank you. Sure, I will create a reproducer and rise a new
ticket.
> Striped pool can't be disabled
> --
>
> Key: IGNITE-7993
> URL: https://issues.apache.org/jira/browse/IGNITE-7993
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.7
>
>
> Javadoc for {{IgniteConfiguration#setStripedPoolSize}} states that striped
> pool can be disabled by providing value less or equal than zero:
> {noformat}
> If set to non-positive value then requests get processed in system pool.
> {noformat}
> However, doing that prevents node from startup, it fails with the following
> exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid
> stripedPool thread pool size (must be greater than 0), actual value: 0
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.validateThreadPoolSize(IgnitionEx.java:2061)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8886) Simultaneous using of BinaryWriter и BinaryRawWriter leads to BinaryObjectException and OOM
Roman Guseinov created IGNITE-8886:
--
Summary: Simultaneous using of BinaryWriter и BinaryRawWriter
leads to BinaryObjectException and OOM
Key: IGNITE-8886
URL: https://issues.apache.org/jira/browse/IGNITE-8886
Project: Ignite
Issue Type: Bug
Components: binary
Affects Versions: 2.5
Reporter: Roman Guseinov
Attachments: BinarylizableInvalidFlag.java, BinarylizableOOM.java
When we use BinaryWriter and BinaryRawWriter simultaneously inside writeBinary
method we can get the following exceptions in the process of deserializing
objects:
1. class org.apache.ignite.binary.BinaryObjectException: Invalid flag value: 115
{code:java}
Exception in thread "main" javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Failed to deserialize object
[typeName=org.apache.ignite.reproducers.fd7550.BinarylizableInvalidFlag$TestBean]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1302)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1732)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:910)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:608)
at
org.apache.ignite.reproducers.fd7550.BinarylizableInvalidFlag.main(BinarylizableInvalidFlag.java:33)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
deserialize object
[typeName=org.apache.ignite.reproducers.fd7550.BinarylizableInvalidFlag$TestBean]
at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7322)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4563)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4537)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1350)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:907)
... 2 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
deserialize object
[typeName=org.apache.ignite.reproducers.fd7550.BinarylizableInvalidFlag$TestBean]
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:909)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:798)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
at
org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:177)
at
org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:67)
at
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
at
org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1764)
at
org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1752)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:679)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:461)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:342)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:216)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture.java:208)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAsync0(GridDhtAtomicCache.java:1390)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1600(GridDhtAtomicCache.java:130)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$16.apply(GridDhtAtomicCache.java:469)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAt
[jira] [Updated] (IGNITE-8884) .NET: CachePartialUpdateException: failed to update keys (using Cache.PutAsync)
[
https://issues.apache.org/jira/browse/IGNITE-8884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Guseinov updated IGNITE-8884:
---
Environment:
Windows 10.
Apache Ignite 2.5.0.
.NETFramework,Version=v4.6.1
Packages:
* Apache.Ignite - 2.5.0
* Apache.Ignite.Log4Net - 2.5.0
* Apache.Ignite.NLog - 2.5.0
* NLog - 4.0.0
was:
* Windows 10.
* Apache Ignite 2.5.0.
* .NETFramework,Version=v4.6.1
Packages:
* Apache.Ignite - 2.5.0
* Apache.Ignite.Log4Net - 2.5.0
* Apache.Ignite.NLog - 2.5.0
* NLog - 4.0.0
> .NET: CachePartialUpdateException: failed to update keys (using
> Cache.PutAsync)
> ---
>
> Key: IGNITE-8884
> URL: https://issues.apache.org/jira/browse/IGNITE-8884
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.5
> Environment: Windows 10.
> Apache Ignite 2.5.0.
> .NETFramework,Version=v4.6.1
> Packages:
> * Apache.Ignite - 2.5.0
> * Apache.Ignite.Log4Net - 2.5.0
> * Apache.Ignite.NLog - 2.5.0
> * NLog - 4.0.0
>
>
>Reporter: Roman Guseinov
>Priority: Major
> Labels: dot_net
> Attachments: Program.cs
>
>
> The issue happens when we try to call PutAsync(KeyObject, ValueObject) where
> ValueObject's field refers to KeyObject. Reproducer is attached.
>
> {code:java}
> Apache.Ignite.Core.Cache.CachePartialUpdateException: Failed to update keys
> (retry update if possible).: [server_node.TradeId [idHash=573136580,
> hash=31459296, Number=2]]
> at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
> at
> System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
> task)
> at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
> at server_node.Program.d__2.MoveNext() in
> C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
> 61
> --- End of stack trace from previous location where exception was thrown ---
> at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
> at
> System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
> task)
> at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
> at server_node.Program.Main(String[] args) in
> C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
> 22
> {code}
>
> Also, when we use the default logger, Cache.PutAsync doesn't throw an
> exception but when we try to get value back from the cache the different
> exception happens:
>
> {code:java}
> System.ArgumentException: Seek before origin: -25
> at Apache.Ignite.Core.Impl.Memory.PlatformMemoryStream.Seek(Int32 offset,
> SeekOrigin origin)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadHandleObject[T](Int32 pos,
> Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String fieldName)
> at lambda_method(Closure , Object , IBinaryReader )
> at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos,
> Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadBinaryObject[T](Boolean
> doDetach)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.Marshaller.Unmarshal[T](IBinaryStream
> stream, Boolean keepBinary)
> at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutLong[TR](Int32 type,
> Action`1 outAction, Func`3 inAction, Func`2 readErrorAction)
> at Apache.Ignite.Core.Impl.Cache.CacheImpl`2.Get(TK key)
> at server_node.Program.d__2.MoveNext() in
> C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
> 62
> --- End of stack trace from previous location where exception was thrown ---
> at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
> at
> System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
> task)
> at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
> at server_node.Program.Main(String[] args) in
> C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
> 22
> {code}
>
> There
[jira] [Created] (IGNITE-8884) .NET: CachePartialUpdateException: failed to update keys (using Cache.PutAsync)
Roman Guseinov created IGNITE-8884:
--
Summary: .NET: CachePartialUpdateException: failed to update keys
(using Cache.PutAsync)
Key: IGNITE-8884
URL: https://issues.apache.org/jira/browse/IGNITE-8884
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.5
Environment: * Windows 10.
* Apache Ignite 2.5.0.
* .NETFramework,Version=v4.6.1
Packages:
* Apache.Ignite - 2.5.0
* Apache.Ignite.Log4Net - 2.5.0
* Apache.Ignite.NLog - 2.5.0
* NLog - 4.0.0
Reporter: Roman Guseinov
Attachments: Program.cs
The issue happens when we try to call PutAsync(KeyObject, ValueObject) where
ValueObject's field refers to KeyObject. Reproducer is attached.
{code:java}
Apache.Ignite.Core.Cache.CachePartialUpdateException: Failed to update keys
(retry update if possible).: [server_node.TradeId [idHash=573136580,
hash=31459296, Number=2]]
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at server_node.Program.d__2.MoveNext() in
C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
61
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at server_node.Program.Main(String[] args) in
C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
22
{code}
Also, when we use the default logger, Cache.PutAsync doesn't throw an
exception but when we try to get value back from the cache the different
exception happens:
{code:java}
System.ArgumentException: Seek before origin: -25
at Apache.Ignite.Core.Impl.Memory.PlatformMemoryStream.Seek(Int32 offset,
SeekOrigin origin)
at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadHandleObject[T](Int32 pos,
Type typeOverride)
at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
typeOverride)
at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String fieldName)
at lambda_method(Closure , Object , IBinaryReader )
at
Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride)
at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos,
Type typeOverride)
at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
typeOverride)
at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadBinaryObject[T](Boolean
doDetach)
at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
typeOverride)
at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride)
at Apache.Ignite.Core.Impl.Binary.Marshaller.Unmarshal[T](IBinaryStream stream,
Boolean keepBinary)
at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutLong[TR](Int32 type,
Action`1 outAction, Func`3 inAction, Func`2 readErrorAction)
at Apache.Ignite.Core.Impl.Cache.CacheImpl`2.Get(TK key)
at server_node.Program.d__2.MoveNext() in
C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
62
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at server_node.Program.Main(String[] args) in
C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
22
{code}
There are two workarounds:
# Do not use the same object as key and the value's field.
# Put data into the cache using the synchronous method.
Reproducer is attached: [^Program.cs]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7993) Striped pool can't be disabled
[
https://issues.apache.org/jira/browse/IGNITE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521998#comment-16521998
]
Roman Guseinov commented on IGNITE-7993:
Hi [~vkulichenko] , thank you for the comments.
According to the conversation with [~yzhdanov] , in this ticket, we just need
to restore an ability to disable striped pool. The additional pool can be the
next step once we create a reproducer.
> Striped pool can't be disabled
> --
>
> Key: IGNITE-7993
> URL: https://issues.apache.org/jira/browse/IGNITE-7993
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.6
>
>
> Javadoc for {{IgniteConfiguration#setStripedPoolSize}} states that striped
> pool can be disabled by providing value less or equal than zero:
> {noformat}
> If set to non-positive value then requests get processed in system pool.
> {noformat}
> However, doing that prevents node from startup, it fails with the following
> exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid
> stripedPool thread pool size (must be greater than 0), actual value: 0
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.validateThreadPoolSize(IgnitionEx.java:2061)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7993) Striped pool can't be disabled
[
https://issues.apache.org/jira/browse/IGNITE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519954#comment-16519954
]
Roman Guseinov commented on IGNITE-7993:
Hi [~vkulichenko] ,
Based on Yakov's requirements, I updated fix and created a new PR
https://github.com/apache/ignite/pull/4235 . Could you please take a look?
TC results:
https://ci.ignite.apache.org/viewLog.html?buildId=1410307&tab=queuedBuildOverviewTab
I've checked 16 new failed tests. Almost all of them were failing on the master
branch or on other PRs with the same errors. Just one test was green before my
PR test:
IgniteWalFormatFileFailoverTest.testFailureHandlerTriggeredFsync [1]
I checked the log and it looks like this fail is not related to my changes.
Thanks in advance.
[1]
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-635689296996716497&tab=testDetails
> Striped pool can't be disabled
> --
>
> Key: IGNITE-7993
> URL: https://issues.apache.org/jira/browse/IGNITE-7993
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.6
>
>
> Javadoc for {{IgniteConfiguration#setStripedPoolSize}} states that striped
> pool can be disabled by providing value less or equal than zero:
> {noformat}
> If set to non-positive value then requests get processed in system pool.
> {noformat}
> However, doing that prevents node from startup, it fails with the following
> exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid
> stripedPool thread pool size (must be greater than 0), actual value: 0
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.validateThreadPoolSize(IgnitionEx.java:2061)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8824) .NET: Invalid header on deserialization
[
https://issues.apache.org/jira/browse/IGNITE-8824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516604#comment-16516604
]
Roman Guseinov commented on IGNITE-8824:
The issue is reproducible on the master branch.
> .NET: Invalid header on deserialization
> ---
>
> Key: IGNITE-8824
> URL: https://issues.apache.org/jira/browse/IGNITE-8824
> Project: Ignite
> Issue Type: Bug
> Components: binary, platforms
>Affects Versions: 2.5
>Reporter: Roman Guseinov
>Priority: Major
> Labels: dot_net
> Attachments: InteropreabilityTest.cs, ServerNode.java
>
>
> The issue happens when we save an object with java.util.Date field in Java
> and retrieves that one on .NET side (DateTime). According to the docs these
> types should be compatible [1].
> {code:java}
> Apache.Ignite.Core.Binary.BinaryObjectException: 'Invalid header on
> deserialization [pos=34, hdr=11]'
> {code}
> The workaround is java.sql.Timestamp instead of Date type.
> Java and C# code examples to reproduce the issue are attached:
> [^ServerNode.java][^InteropreabilityTest.cs]
> [1]
> [https://apacheignite-net.readme.io/v2.1/docs/platform-interoperability#section-type-compatibility]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8824) .NET: Invalid header on deserialization
Roman Guseinov created IGNITE-8824:
--
Summary: .NET: Invalid header on deserialization
Key: IGNITE-8824
URL: https://issues.apache.org/jira/browse/IGNITE-8824
Project: Ignite
Issue Type: Bug
Components: binary, platforms
Affects Versions: 2.5
Reporter: Roman Guseinov
Attachments: InteropreabilityTest.cs, ServerNode.java
The issue happens when we save an object with java.util.Date field in Java and
retrieves that one on .NET side (DateTime). According to the docs these types
should be compatible [1].
{code:java}
Apache.Ignite.Core.Binary.BinaryObjectException: 'Invalid header on
deserialization [pos=34, hdr=11]'
{code}
The workaround is java.sql.Timestamp instead of Date type.
Java and C# code examples to reproduce the issue are attached:
[^ServerNode.java][^InteropreabilityTest.cs]
[1]
[https://apacheignite-net.readme.io/v2.1/docs/platform-interoperability#section-type-compatibility]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8786) session.removeAttribute does not work as expected
[ https://issues.apache.org/jira/browse/IGNITE-8786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-8786: --- Description: Simple Maven project: [https://github.com/gromtech/ignite-web-session-example] What I'm noticing is that session.removeAttribute doesn't really remove the attribute, it only sets the value to null. I'm not sure if this is a setup issue on my end or what. I thought this might be related to jsf, removed jsf and the issue persists. Environment: - Ignite 2.5.0 (1 server node [^server-config.xml]) - Java 8 was: Simple maven project: [https://github.com/gromtech/ignite-web-session-example] What I'm noticing is that session.removeAttribute doesn't really remove the attribute, it only sets the value to null. I'm not sure if this is a setup issue on my end or what. I thought this might be related to jsf, removed jsf and the issue persists. Probably, the closest issue that I could find to my particular issue was: [https://github.com/apache/ignite/pull/2243] I patched my local ignite repo with #2243 , redeployed to tomcat and 2 ignite nodes but am seeing the same issue. The closest issue that I could find to my particular issue was: [https://github.com/apache/ignite/pull/2243] My setup (client/server): - Ignite 2.5.0 (1 server node) - Java 8 > session.removeAttribute does not work as expected > - > > Key: IGNITE-8786 > URL: https://issues.apache.org/jira/browse/IGNITE-8786 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4, 2.5 > Environment: Java 8, Java 9, Java 10 > Ignite 2.4 and Ignite 2.5 >Reporter: Dana Shaw >Priority: Major > Attachments: server-config.xml > > > Simple Maven project: [https://github.com/gromtech/ignite-web-session-example] > What I'm noticing is that session.removeAttribute doesn't really remove the > attribute, it only sets the value to null. I'm not sure if this is a setup > issue on my end or what. I thought this might be related to jsf, removed jsf > and the issue persists. > Environment: > - Ignite 2.5.0 (1 server node [^server-config.xml]) > - Java 8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8786) session.removeAttribute does not work as expected
[ https://issues.apache.org/jira/browse/IGNITE-8786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-8786: --- Attachment: server-config.xml > session.removeAttribute does not work as expected > - > > Key: IGNITE-8786 > URL: https://issues.apache.org/jira/browse/IGNITE-8786 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4, 2.5 > Environment: Java 8, Java 9, Java 10 > Ignite 2.4 and Ignite 2.5 >Reporter: Dana Shaw >Priority: Major > Attachments: server-config.xml > > > Simple maven project: [https://github.com/gromtech/ignite-web-session-example] > What I'm noticing is that session.removeAttribute doesn't really remove the > attribute, it only sets the value to null. I'm not sure if this is a setup > issue on my end or what. I thought this might be related to jsf, removed jsf > and the issue persists. > > Probably, the closest issue that I could find to my particular issue was: > [https://github.com/apache/ignite/pull/2243] > I patched my local ignite repo with #2243 , redeployed to tomcat and 2 > ignite nodes but am seeing the same issue. > The closest issue that I could find to my particular issue was: > [https://github.com/apache/ignite/pull/2243] > My setup (client/server): > - Ignite 2.5.0 (1 server node) > - Java 8 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8786) session.removeAttribute does not work as expected
[ https://issues.apache.org/jira/browse/IGNITE-8786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-8786: --- Description: Simple maven project: [https://github.com/gromtech/ignite-web-session-example] What I'm noticing is that session.removeAttribute doesn't really remove the attribute, it only sets the value to null. I'm not sure if this is a setup issue on my end or what. I thought this might be related to jsf, removed jsf and the issue persists. Probably, the closest issue that I could find to my particular issue was: [https://github.com/apache/ignite/pull/2243] I patched my local ignite repo with #2243 , redeployed to tomcat and 2 ignite nodes but am seeing the same issue. The closest issue that I could find to my particular issue was: [https://github.com/apache/ignite/pull/2243] My setup (client/server): - Ignite 2.5.0 (1 server node) - Java 8 was: Simple maven project: [https://github.com/gromtech/ignite-web-session-example] What I'm noticing is that session.removeAttribute doesn't really remove the attribute, it only sets the value to null. I'm not sure if this is a setup issue on my end or what. I thought this might be related to jsf, removed jsf and the issue persists. Thanks in advance and please help! dshaw The closest issue that I could find to my particular issue was: [https://github.com/apache/ignite/pull/2243] I patched my local ignite repo with #2243 , redeployed to tomcat and 2 ignite nodes but am seeing the same issue. The closest issue that I could find to my particular issue was: [https://github.com/apache/ignite/pull/2243] My setup (client/server): - Ignite 2.5.0 (2 node cluster) - Apache Tomcat 7 - Java 9 tomcat setenv.sh #!/bin/sh export JAVA_HOME=/opt/java/jdk-10.0.1 export PATH=$JAVA_HOME/bin:$PATH export CATALINA_OPTS="--add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports java.base/sun.nio.ch=ALL-UNNAMED --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED --add-modules java.xml.bind" export CATALINA_HOME=/opt/apache/apache-tomcat-7.0.86_node # ## ### # Config use by 3 tomcat notes client-config.xml (used by tomcat 7) http://www.springframework.org/schema/beans]" xmlns:xsi="[http://www.w3.org/2001/XMLSchema-instance]" xmlns:util="[http://www.springframework.org/schema/util]" xsi:schemaLocation=" [http://www.springframework.org/schema/beans] [http://www.springframework.org/schema/beans/spring-beans.xsd] [http://www.springframework.org/schema/util] [http://www.springframework.org/schema/util/spring-util.xsd]";> 172.24.2.156:47500..47509 172.24.3.28:47500..47509 # ## ### # Config use by 2 ignite nodes http://www.springframework.org/schema/beans]" xmlns:xsi="[http://www.w3.org/2001/XMLSchema-instance]" xmlns:util="[http://www.springframework.org/schema/util]" xsi:schemaLocation=" [http://www.springframework.org/schema/beans] [http://www.springframework.org/schema/beans/spring-beans.xsd] [http://www.springframework.org/schema/util] [http://www.springframework.org/schema/util/spring-util.xsd]";> 172.24.2.156:47500..47509 172.24.3.28:47500..47509 > session.removeAttribute does not work as expected > - > > Key: IGNITE-8786 > URL: https://issues.apache.org/jira/browse/IGNITE-8786 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4, 2.5 > Environment: Java 8, Java 9, Java 10 > Ignite 2.4 and Ignite 2.5 >Reporter: Dana Shaw >Priority: Major > > Simple maven project: [https://github.com/gromtech/ignite-web-session-example] > What I'm noticing is that session.removeAttribute doesn't really remove the > attribute, it only sets the value to null. I'm not
[jira] [Updated] (IGNITE-8786) session.removeAttribute does not work as expected
[ https://issues.apache.org/jira/browse/IGNITE-8786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Guseinov updated IGNITE-8786: --- Description: Simple maven project: [https://github.com/gromtech/ignite-web-session-example] What I'm noticing is that session.removeAttribute doesn't really remove the attribute, it only sets the value to null. I'm not sure if this is a setup issue on my end or what. I thought this might be related to jsf, removed jsf and the issue persists. Thanks in advance and please help! dshaw The closest issue that I could find to my particular issue was: [https://github.com/apache/ignite/pull/2243] I patched my local ignite repo with #2243 , redeployed to tomcat and 2 ignite nodes but am seeing the same issue. The closest issue that I could find to my particular issue was: [https://github.com/apache/ignite/pull/2243] My setup (client/server): - Ignite 2.5.0 (2 node cluster) - Apache Tomcat 7 - Java 9 tomcat setenv.sh #!/bin/sh export JAVA_HOME=/opt/java/jdk-10.0.1 export PATH=$JAVA_HOME/bin:$PATH export CATALINA_OPTS="--add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports java.base/sun.nio.ch=ALL-UNNAMED --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED --add-modules java.xml.bind" export CATALINA_HOME=/opt/apache/apache-tomcat-7.0.86_node # ## ### # Config use by 3 tomcat notes client-config.xml (used by tomcat 7) http://www.springframework.org/schema/beans]" xmlns:xsi="[http://www.w3.org/2001/XMLSchema-instance]" xmlns:util="[http://www.springframework.org/schema/util]" xsi:schemaLocation=" [http://www.springframework.org/schema/beans] [http://www.springframework.org/schema/beans/spring-beans.xsd] [http://www.springframework.org/schema/util] [http://www.springframework.org/schema/util/spring-util.xsd]";> 172.24.2.156:47500..47509 172.24.3.28:47500..47509 # ## ### # Config use by 2 ignite nodes http://www.springframework.org/schema/beans]" xmlns:xsi="[http://www.w3.org/2001/XMLSchema-instance]" xmlns:util="[http://www.springframework.org/schema/util]" xsi:schemaLocation=" [http://www.springframework.org/schema/beans] [http://www.springframework.org/schema/beans/spring-beans.xsd] [http://www.springframework.org/schema/util] [http://www.springframework.org/schema/util/spring-util.xsd]";> 172.24.2.156:47500..47509 172.24.3.28:47500..47509 was: Sample project: [https://github.com/daynok/ignite-webapp] What I'm noticing is that session.removeAttribute doesn't really remove the attribute, it only sets the value to null. I'm not sure if this is a setup issue on my end or what. I thought this might be related to jsf, removed jsf and the issue persists. Thanks in advance and please help! dshaw The closest issue that I could find to my particular issue was: [https://github.com/apache/ignite/pull/2243] I patched my local ignite repo with #2243 , redeployed to tomcat and 2 ignite nodes but am seeing the same issue. The closest issue that I could find to my particular issue was: [https://github.com/apache/ignite/pull/2243] My setup (client/server): - Ignite 2.5.0 (2 node cluster) - Apache Tomcat 7 - Java 9 tomcat setenv.sh #!/bin/sh export JAVA_HOME=/opt/java/jdk-10.0.1 export PATH=$JAVA_HOME/bin:$PATH export CATALINA_OPTS="--add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports java.base/sun.nio.ch=ALL-UNNAMED --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED --add-modules java.xml.bind" export CATALINA_HOME=/opt/apache/apache-tomcat-7.0.86_node # Config use by 3 tomcat notes client-config.xml (used by tomcat 7) http://www.springframework.org/schema/beans]" xmlns:xsi="[http://w
