[jira] [Commented] (IGNITE-7010) Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
[
https://issues.apache.org/jira/browse/IGNITE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265147#comment-16265147
]
Krzysztof Chmielewski commented on IGNITE-7010:
---
fixed with
{code}
node.compute(node.cluster().forLocal()).runAsync(
// cache destroy Runnable
);
{code}
> Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
> ---
>
> Key: IGNITE-7010
> URL: https://issues.apache.org/jira/browse/IGNITE-7010
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Krzysztof Chmielewski
>
> Ignite hangs trying to delete cache as a response to Ignite Event
> EventType.EVT_NODE_LEFT.
> Code to reproduce this issue is available at
> https://github.com/kristoffSC/IgniteHang
> Reproduce instructions:
> # Put break points in ServerStarter.java line 40 and 42.
> # Start ServerStarter as Java Application in Debug mode.
> # Start ClientStarter as Java Application. After ClientStarter ends,
> ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
> Try skip to next line ({code}ignite.destroyCache("testCache"){code}) and then
> try skip one more line. Ignite will hang at line 41.
> This "hang" prevents other nodes from connecting to this running/hanging
> Ignite Server.
> Thread that stuck is "disco-event-worker". It waits on {code} return
> stopFut.get() {code} in IgniteKernel.class at line 3146
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (IGNITE-7010) Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
[
https://issues.apache.org/jira/browse/IGNITE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krzysztof Chmielewski closed IGNITE-7010.
-
> Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
> ---
>
> Key: IGNITE-7010
> URL: https://issues.apache.org/jira/browse/IGNITE-7010
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Krzysztof Chmielewski
>
> Ignite hangs trying to delete cache as a response to Ignite Event
> EventType.EVT_NODE_LEFT.
> Code to reproduce this issue is available at
> https://github.com/kristoffSC/IgniteHang
> Reproduce instructions:
> # Put break points in ServerStarter.java line 40 and 42.
> # Start ServerStarter as Java Application in Debug mode.
> # Start ClientStarter as Java Application. After ClientStarter ends,
> ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
> Try skip to next line ({code}ignite.destroyCache("testCache"){code}) and then
> try skip one more line. Ignite will hang at line 41.
> This "hang" prevents other nodes from connecting to this running/hanging
> Ignite Server.
> Thread that stuck is "disco-event-worker". It waits on {code} return
> stopFut.get() {code} in IgniteKernel.class at line 3146
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-7010) Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
[
https://issues.apache.org/jira/browse/IGNITE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krzysztof Chmielewski updated IGNITE-7010:
--
Description:
Ignite hangs trying to delete cache as a response to Ignite Event
EventType.EVT_NODE_LEFT.
Code to reproduce this issue is available at
https://github.com/kristoffSC/IgniteHang
Reproduce instructions:
# Put break points in ServerStarter.java line 40 and 42.
# Start ServerStarter as Java Application in Debug mode.
# Start ClientStarter as Java Application. After ClientStarter ends,
ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
Try skip to next line (ignite.destroyCache("testCache")) and then
try skip one more line. Ignite will hang at line 41.
This "hang" prevents other nodes from connecting to this running/hanging Ignite
Server.
Thread that stuck is "disco-event-worker". It waits on {code} return
stopFut.get() {code} in IgniteKernel.class at line 3146
was:
Ignite hangs trying to delete cache as a response to Ignite Event
EventType.EVT_NODE_LEFT.
Code to reproduce this issue is available at
https://github.com/kristoffSC/IgniteHang
Reproduce instructions:
# Put break points in ServerStarter.java line 40 and 42.
# Start ServerStarter as Java Application in Debug mode.
# Start ClientStarter as Java Application. After ClientStarter ends,
ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
Try skip to next line (ignite.destroyCache("testCache")) and then try skip one
more line. Ignite will hang at line 41.
This "hang" prevents other nodes from connecting to this running/hanging Ignite
Server.
Thread that stuck is "disco-event-worker". It waits on {code} return
stopFut.get() {code} in IgniteKernel.class at line 3146
> Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
> ---
>
> Key: IGNITE-7010
> URL: https://issues.apache.org/jira/browse/IGNITE-7010
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Krzysztof Chmielewski
>
> Ignite hangs trying to delete cache as a response to Ignite Event
> EventType.EVT_NODE_LEFT.
> Code to reproduce this issue is available at
> https://github.com/kristoffSC/IgniteHang
> Reproduce instructions:
> # Put break points in ServerStarter.java line 40 and 42.
> # Start ServerStarter as Java Application in Debug mode.
> # Start ClientStarter as Java Application. After ClientStarter ends,
> ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
> Try skip to next line (ignite.destroyCache("testCache")) and
> then try skip one more line. Ignite will hang at line 41.
> This "hang" prevents other nodes from connecting to this running/hanging
> Ignite Server.
> Thread that stuck is "disco-event-worker". It waits on {code} return
> stopFut.get() {code} in IgniteKernel.class at line 3146
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-7010) Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
[
https://issues.apache.org/jira/browse/IGNITE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krzysztof Chmielewski updated IGNITE-7010:
--
Description:
Ignite hangs trying to delete cache as a response to Ignite Event
EventType.EVT_NODE_LEFT.
Code to reproduce this issue is available at
https://github.com/kristoffSC/IgniteHang
Reproduce instructions:
# Put break points in ServerStarter.java line 40 and 42.
# Start ServerStarter as Java Application in Debug mode.
# Start ClientStarter as Java Application. After ClientStarter ends,
ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
Try skip to next line ({code}ignite.destroyCache("testCache"){code}) and then
try skip one more line. Ignite will hang at line 41.
This "hang" prevents other nodes from connecting to this running/hanging Ignite
Server.
Thread that stuck is "disco-event-worker". It waits on {code} return
stopFut.get() {code} in IgniteKernel.class at line 3146
was:
Ignite hangs trying to delete cache as a response to Ignite Event
EventType.EVT_NODE_LEFT.
Code to reproduce this issue is available at
https://github.com/kristoffSC/IgniteHang
Reproduce instructions:
# Put break points in ServerStarter.java line 40 and 42.
# Start ServerStarter as Java Application in Debug mode.
# Start ClientStarter as Java Application. After ClientStarter ends,
ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
Try skip to next line (ignite.destroyCache("testCache")) and then
try skip one more line. Ignite will hang at line 41.
This "hang" prevents other nodes from connecting to this running/hanging Ignite
Server.
Thread that stuck is "disco-event-worker". It waits on {code} return
stopFut.get() {code} in IgniteKernel.class at line 3146
> Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
> ---
>
> Key: IGNITE-7010
> URL: https://issues.apache.org/jira/browse/IGNITE-7010
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Krzysztof Chmielewski
>
> Ignite hangs trying to delete cache as a response to Ignite Event
> EventType.EVT_NODE_LEFT.
> Code to reproduce this issue is available at
> https://github.com/kristoffSC/IgniteHang
> Reproduce instructions:
> # Put break points in ServerStarter.java line 40 and 42.
> # Start ServerStarter as Java Application in Debug mode.
> # Start ClientStarter as Java Application. After ClientStarter ends,
> ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
> Try skip to next line ({code}ignite.destroyCache("testCache"){code}) and then
> try skip one more line. Ignite will hang at line 41.
> This "hang" prevents other nodes from connecting to this running/hanging
> Ignite Server.
> Thread that stuck is "disco-event-worker". It waits on {code} return
> stopFut.get() {code} in IgniteKernel.class at line 3146
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-7010) Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
[
https://issues.apache.org/jira/browse/IGNITE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krzysztof Chmielewski updated IGNITE-7010:
--
Description:
Ignite hangs trying to delete cache as a response to Ignite Event
EventType.EVT_NODE_LEFT.
Code to reproduce this issue is available at
https://github.com/kristoffSC/IgniteHang
Reproduce instructions:
# Put break points in ServerStarter.java line 40 and 42.
# Start ServerStarter as Java Application in Debug mode.
# Start ClientStarter as Java Application. After ClientStarter ends,
ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
Try skip to next line (ignite.destroyCache("testCache")) and then try skip one
more line. Ignite will hang at line 41.
This "hang" prevents other nodes from connecting to this running/hanging Ignite
Server.
Thread that stuck is "disco-event-worker". It waits on {code} return
stopFut.get() {code} in IgniteKernel.class at line 3146
was:
Ignite hangs trying to delete cache as a response to Ignite Event
EventType.EVT_NODE_LEFT.
Code to reproduce this issue is available at
https://github.com/kristoffSC/IgniteHang
Reproduce instructions:
# Put break points in ServerStarter.java line 40 and 42.
# Start ServerStarter as Java Application in Debug mode.
# Start ClientStarter as Java Application. After ClientStarter ends,
ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
Try skip to next line (ignite.destroyCache("testCache");) and then try skip one
more line. Ignite will hang at line 41.
This "hang" prevents other nodes from connecting to this running/hanging Ignite
Server.
Thread that stuck is "disco-event-worker". It waits on {code} return
stopFut.get() {code} in IgniteKernel.class at line 3146
> Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
> ---
>
> Key: IGNITE-7010
> URL: https://issues.apache.org/jira/browse/IGNITE-7010
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Krzysztof Chmielewski
>
> Ignite hangs trying to delete cache as a response to Ignite Event
> EventType.EVT_NODE_LEFT.
> Code to reproduce this issue is available at
> https://github.com/kristoffSC/IgniteHang
> Reproduce instructions:
> # Put break points in ServerStarter.java line 40 and 42.
> # Start ServerStarter as Java Application in Debug mode.
> # Start ClientStarter as Java Application. After ClientStarter ends,
> ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
> Try skip to next line (ignite.destroyCache("testCache")) and then try skip
> one more line. Ignite will hang at line 41.
> This "hang" prevents other nodes from connecting to this running/hanging
> Ignite Server.
> Thread that stuck is "disco-event-worker". It waits on {code} return
> stopFut.get() {code} in IgniteKernel.class at line 3146
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-7010) Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
[
https://issues.apache.org/jira/browse/IGNITE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krzysztof Chmielewski updated IGNITE-7010:
--
Description:
Ignite hangs trying to delete cache as a response to Ignite Event
EventType.EVT_NODE_LEFT.
Code to reproduce this issue is available at
https://github.com/kristoffSC/IgniteHang
Reproduce instructions:
# Put break points in ServerStarter.java line 40 and 42.
# Start ServerStarter as Java Application in Debug mode.
# Start ClientStarter as Java Application. After ClientStarter ends,
ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
Try skip to next line (ignite.destroyCache("testCache");) and then try skip one
more line. Ignite will hang at line 41.
This "hang" prevents other nodes from connecting to this running/hanging Ignite
Server.
Thread that stuck is "disco-event-worker". It waits on {code} return
stopFut.get() {code} in IgniteKernel.class at line 3146
was:
Ignite hangs trying to delete cache as a response to Ignite Event
EventType.EVT_NODE_LEFT.
Code to reproduce this issue is available at
https://github.com/kristoffSC/IgniteHang
Reproduce instructions:
# Put break points in ServerStarter.java line 40 and 42.
## Start ServerStarter as Java Application in Debug mode.
### Start ClientStarter as Java Application. After ClientStarter ends,
ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
Try skip to next line (ignite.destroyCache("testCache");) and then try skip one
more line. Ignite will hang at line 41.
This "hang" prevents other nodes from connecting to this running/hanging Ignite
Server.
Thread that stuck is "disco-event-worker". It waits on {code} return
stopFut.get() {code} in IgniteKernel.class at line 3146
> Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
> ---
>
> Key: IGNITE-7010
> URL: https://issues.apache.org/jira/browse/IGNITE-7010
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Krzysztof Chmielewski
>
> Ignite hangs trying to delete cache as a response to Ignite Event
> EventType.EVT_NODE_LEFT.
> Code to reproduce this issue is available at
> https://github.com/kristoffSC/IgniteHang
> Reproduce instructions:
> # Put break points in ServerStarter.java line 40 and 42.
> # Start ServerStarter as Java Application in Debug mode.
> # Start ClientStarter as Java Application. After ClientStarter ends,
> ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
> Try skip to next line (ignite.destroyCache("testCache");) and then try skip
> one more line. Ignite will hang at line 41.
> This "hang" prevents other nodes from connecting to this running/hanging
> Ignite Server.
> Thread that stuck is "disco-event-worker". It waits on {code} return
> stopFut.get() {code} in IgniteKernel.class at line 3146
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-7010) Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
Krzysztof Chmielewski created IGNITE-7010:
-
Summary: Ignite hangs on cache destroy called from
IgniteBiPredicate - Ignite Events
Key: IGNITE-7010
URL: https://issues.apache.org/jira/browse/IGNITE-7010
Project: Ignite
Issue Type: Bug
Affects Versions: 2.3
Reporter: Krzysztof Chmielewski
Ignite hangs trying to delete cache as a response to Ignite Event
EventType.EVT_NODE_LEFT.
Code to reproduce this issue is available at
https://github.com/kristoffSC/IgniteHang
Reproduce instructions:
# Put break points in ServerStarter.java line 40 and 42.
## Start ServerStarter as Java Application in Debug mode.
### Start ClientStarter as Java Application. After ClientStarter ends,
ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP).
Try skip to next line (ignite.destroyCache("testCache");) and then try skip one
more line. Ignite will hang at line 41.
This "hang" prevents other nodes from connecting to this running/hanging Ignite
Server.
Thread that stuck is "disco-event-worker". It waits on {code} return
stopFut.get() {code} in IgniteKernel.class at line 3146
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-6234) [Test failure] GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
[
https://issues.apache.org/jira/browse/IGNITE-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191043#comment-16191043
]
Krzysztof Chmielewski edited comment on IGNITE-6234 at 10/12/17 9:14 AM:
-
Hi,
I'm facing this issue to, but in a slightly different scenario.
However I wonder how *schemaIds* can be null since *BinaryMetadata* constructor
sets this field to *Collections.emptySet();* in a "worst" case.
Unless the *BinaryMetadata* is also deserialized and its parameterized
constructor is not called.
was (Author: kristoffsc):
Hi,
I'm facing this issue to, but in a slightly different scenario.
However I wonder how *schemaIds* can be null since *BinaryMetadata* constructor
sets this field to *Collections.emptySet();* in a "worst" case.
Unless the *BinaryMetadata* is also deserialized and its constructor is not
called.
> [Test failure]
> GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
> ---
>
> Key: IGNITE-6234
> URL: https://issues.apache.org/jira/browse/IGNITE-6234
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Labels: MakeTeamcityGreenAgain
>
> Test reproducible locally although with a very low probability.
> I wasn't able to reproduce it starting test in isolation but managed to do it
> starting *GridCacheClientModesTcpClientDiscoveryAbstractTest* 50 times in a
> row observing from 1 to 3 failures.
> Test run with failed test is available
> [here|https://ci.ignite.apache.org/viewLog.html?buildId=798538=buildResultsDiv=Ignite20Tests_IgniteCache].
> It seems that when client requests value of custom class from near cache it
> may see BinaryMetadata for this class with no schema.
> Test fails with the following exception:
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.binary.BinaryMetadata.hasSchema(BinaryMetadata.java:189)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:517)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1237)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2005)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:183)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:830)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:794)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:161)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:41)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1734)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1889)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1828)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.loadEntries(GridNearGetFuture.java:752)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.access$000(GridNearGetFuture.java:68)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture$MiniFuture.onResult(GridNearGetFuture.java:1012)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onResult(GridNearGetFuture.java:215)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearCacheAdapter.processGetResponse(GridNearCacheAdapter.java:294)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTransactionalCache$1.apply(GridNearTransactionalCache.java:92)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTransactionalCache$1.apply(GridNearTransactionalCache.java:90)
> at
>
[jira] [Comment Edited] (IGNITE-6234) [Test failure] GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
[
https://issues.apache.org/jira/browse/IGNITE-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16193826#comment-16193826
]
Krzysztof Chmielewski edited comment on IGNITE-6234 at 10/5/17 10:16 PM:
-
Hi Team,
my previous post got me thinking and I believe I've found the root cause of
this issue. Problem is during deserialization and it is in *readFrom(Datainput
in)* method.
Please see my pull request for a details.
https://github.com/apache/ignite/pull/2811
Comparing *readFrom(Datainput in)* method to BinaryMetadata constructor I've
noticed that *schemaId* field is not initialized as an empty Set if *schemas*
field is *null* as it is in line 118 for example.
So *readFrom(Datainput in)* is missing this part.
was (Author: kristoffsc):
Hi Team,
my previous post got me thinking and I believe I've found the root cause of
this issue. Problem is in *readFrom(Datainput in)* method.
Please see my pull request for a details.
https://github.com/apache/ignite/pull/2811
Comparing *readFrom(Datainput in)* method to BinaryMetadata constructor I've
noticed that *schemaId* field is not initialized as an empty Set if *schemas*
field is *null* as it is in line 118 for example.
So *readFrom(Datainput in)* is missing this part.
> [Test failure]
> GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
> ---
>
> Key: IGNITE-6234
> URL: https://issues.apache.org/jira/browse/IGNITE-6234
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Labels: MakeTeamcityGreenAgain
>
> Test reproducible locally although with a very low probability.
> I wasn't able to reproduce it starting test in isolation but managed to do it
> starting *GridCacheClientModesTcpClientDiscoveryAbstractTest* 50 times in a
> row observing from 1 to 3 failures.
> Test run with failed test is available
> [here|https://ci.ignite.apache.org/viewLog.html?buildId=798538=buildResultsDiv=Ignite20Tests_IgniteCache].
> It seems that when client requests value of custom class from near cache it
> may see BinaryMetadata for this class with no schema.
> Test fails with the following exception:
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.binary.BinaryMetadata.hasSchema(BinaryMetadata.java:189)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:517)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1237)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2005)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:183)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:830)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:794)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:161)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:41)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1734)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1889)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1828)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.loadEntries(GridNearGetFuture.java:752)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.access$000(GridNearGetFuture.java:68)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture$MiniFuture.onResult(GridNearGetFuture.java:1012)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onResult(GridNearGetFuture.java:215)
> at
>
[jira] [Comment Edited] (IGNITE-6234) [Test failure] GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
[
https://issues.apache.org/jira/browse/IGNITE-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16193826#comment-16193826
]
Krzysztof Chmielewski edited comment on IGNITE-6234 at 10/5/17 10:16 PM:
-
Hi Team,
my previous post got me thinking and I believe I've found the root cause of
this issue. Problem is during the deserialization and it is in
*readFrom(Datainput in)* method.
Please see my pull request for a details.
https://github.com/apache/ignite/pull/2811
Comparing *readFrom(Datainput in)* method to BinaryMetadata constructor I've
noticed that *schemaId* field is not initialized as an empty Set if *schemas*
field is *null* as it is in line 118 for example.
So *readFrom(Datainput in)* is missing this part.
was (Author: kristoffsc):
Hi Team,
my previous post got me thinking and I believe I've found the root cause of
this issue. Problem is during deserialization and it is in *readFrom(Datainput
in)* method.
Please see my pull request for a details.
https://github.com/apache/ignite/pull/2811
Comparing *readFrom(Datainput in)* method to BinaryMetadata constructor I've
noticed that *schemaId* field is not initialized as an empty Set if *schemas*
field is *null* as it is in line 118 for example.
So *readFrom(Datainput in)* is missing this part.
> [Test failure]
> GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
> ---
>
> Key: IGNITE-6234
> URL: https://issues.apache.org/jira/browse/IGNITE-6234
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Labels: MakeTeamcityGreenAgain
>
> Test reproducible locally although with a very low probability.
> I wasn't able to reproduce it starting test in isolation but managed to do it
> starting *GridCacheClientModesTcpClientDiscoveryAbstractTest* 50 times in a
> row observing from 1 to 3 failures.
> Test run with failed test is available
> [here|https://ci.ignite.apache.org/viewLog.html?buildId=798538=buildResultsDiv=Ignite20Tests_IgniteCache].
> It seems that when client requests value of custom class from near cache it
> may see BinaryMetadata for this class with no schema.
> Test fails with the following exception:
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.binary.BinaryMetadata.hasSchema(BinaryMetadata.java:189)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:517)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1237)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2005)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:183)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:830)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:794)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:161)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:41)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1734)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1889)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1828)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.loadEntries(GridNearGetFuture.java:752)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.access$000(GridNearGetFuture.java:68)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture$MiniFuture.onResult(GridNearGetFuture.java:1012)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onResult(GridNearGetFuture.java:215)
> at
>
[jira] [Commented] (IGNITE-6234) [Test failure] GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
[
https://issues.apache.org/jira/browse/IGNITE-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16193826#comment-16193826
]
Krzysztof Chmielewski commented on IGNITE-6234:
---
Hi Team,
my previous post got me thinking and I believe I've found the root cause of
this issue. Problem is in *readFrom(Datainput in)* method.
Please see my pull request for a details.
https://github.com/apache/ignite/pull/2811
Comparing *readFrom(Datainput in)* method to BinaryMetadata constructor I've
noticed that *schemaId* field is not initialized as an empty Set if *schemas*
field is *null* as it is in line 118 for example.
So *readFrom(Datainput in)* is missing this part.
> [Test failure]
> GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
> ---
>
> Key: IGNITE-6234
> URL: https://issues.apache.org/jira/browse/IGNITE-6234
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Labels: MakeTeamcityGreenAgain
>
> Test reproducible locally although with a very low probability.
> I wasn't able to reproduce it starting test in isolation but managed to do it
> starting *GridCacheClientModesTcpClientDiscoveryAbstractTest* 50 times in a
> row observing from 1 to 3 failures.
> Test run with failed test is available
> [here|https://ci.ignite.apache.org/viewLog.html?buildId=798538=buildResultsDiv=Ignite20Tests_IgniteCache].
> It seems that when client requests value of custom class from near cache it
> may see BinaryMetadata for this class with no schema.
> Test fails with the following exception:
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.binary.BinaryMetadata.hasSchema(BinaryMetadata.java:189)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:517)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1237)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2005)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:183)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:830)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:794)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:161)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:41)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1734)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1889)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1828)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.loadEntries(GridNearGetFuture.java:752)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.access$000(GridNearGetFuture.java:68)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture$MiniFuture.onResult(GridNearGetFuture.java:1012)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onResult(GridNearGetFuture.java:215)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearCacheAdapter.processGetResponse(GridNearCacheAdapter.java:294)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTransactionalCache$1.apply(GridNearTransactionalCache.java:92)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTransactionalCache$1.apply(GridNearTransactionalCache.java:90)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
>
[jira] [Comment Edited] (IGNITE-6234) [Test failure] GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
[
https://issues.apache.org/jira/browse/IGNITE-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191043#comment-16191043
]
Krzysztof Chmielewski edited comment on IGNITE-6234 at 10/5/17 11:29 AM:
-
Hi,
I'm facing this issue to, but in a slightly different scenario.
However I wonder how *schemaIds* can be null since *BinaryMetadata* constructor
sets this field to *Collections.emptySet();* in a "worst" case.
Unless the *BinaryMetadata* is also deserialized and its constructor is not
called.
was (Author: kristoffsc):
Hi,
I'm facing this issue to, but in a slightly different scenario.
However I wonder how *schemaIds* can be null since *BinaryMetadata* constructor
sets this field to *Collections.emptySet();* in a "worst" case.
> [Test failure]
> GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
> ---
>
> Key: IGNITE-6234
> URL: https://issues.apache.org/jira/browse/IGNITE-6234
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Labels: MakeTeamcityGreenAgain
>
> Test reproducible locally although with a very low probability.
> I wasn't able to reproduce it starting test in isolation but managed to do it
> starting *GridCacheClientModesTcpClientDiscoveryAbstractTest* 50 times in a
> row observing from 1 to 3 failures.
> Test run with failed test is available
> [here|https://ci.ignite.apache.org/viewLog.html?buildId=798538=buildResultsDiv=Ignite20Tests_IgniteCache].
> It seems that when client requests value of custom class from near cache it
> may see BinaryMetadata for this class with no schema.
> Test fails with the following exception:
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.binary.BinaryMetadata.hasSchema(BinaryMetadata.java:189)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:517)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1237)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2005)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:183)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:830)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:794)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:161)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:41)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1734)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1889)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1828)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.loadEntries(GridNearGetFuture.java:752)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.access$000(GridNearGetFuture.java:68)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture$MiniFuture.onResult(GridNearGetFuture.java:1012)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onResult(GridNearGetFuture.java:215)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearCacheAdapter.processGetResponse(GridNearCacheAdapter.java:294)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTransactionalCache$1.apply(GridNearTransactionalCache.java:92)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTransactionalCache$1.apply(GridNearTransactionalCache.java:90)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
>
[jira] [Comment Edited] (IGNITE-6234) [Test failure] GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
[
https://issues.apache.org/jira/browse/IGNITE-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191043#comment-16191043
]
Krzysztof Chmielewski edited comment on IGNITE-6234 at 10/4/17 9:30 AM:
Hi,
I'm facing this issue to, but in a slightly different scenario.
However I wonder how *schemaIds* can be null since *BinaryMetadata* constructor
sets this field to *Collections.emptySet();* in a "worst" case.
was (Author: kristoffsc):
Hi,
I'm facing this issue to, but in slightly different scenario.
However I wonder how *schemaIds* can be null since *BinaryMetadata* constructor
sets this field to *Collections.emptySet();* in a "worst" case.
> [Test failure]
> GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
> ---
>
> Key: IGNITE-6234
> URL: https://issues.apache.org/jira/browse/IGNITE-6234
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Labels: MakeTeamcityGreenAgain
>
> Test reproducible locally although with a very low probability.
> I wasn't able to reproduce it starting test in isolation but managed to do it
> starting *GridCacheClientModesTcpClientDiscoveryAbstractTest* 50 times in a
> row observing from 1 to 3 failures.
> Test run with failed test is available
> [here|https://ci.ignite.apache.org/viewLog.html?buildId=798538=buildResultsDiv=Ignite20Tests_IgniteCache].
> It seems that when client requests value of custom class from near cache it
> may see BinaryMetadata for this class with no schema.
> Test fails with the following exception:
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.binary.BinaryMetadata.hasSchema(BinaryMetadata.java:189)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:517)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1237)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2005)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:183)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:830)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:794)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:161)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:41)
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1734)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1889)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1828)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.loadEntries(GridNearGetFuture.java:752)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.access$000(GridNearGetFuture.java:68)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture$MiniFuture.onResult(GridNearGetFuture.java:1012)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onResult(GridNearGetFuture.java:215)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearCacheAdapter.processGetResponse(GridNearCacheAdapter.java:294)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTransactionalCache$1.apply(GridNearTransactionalCache.java:92)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTransactionalCache$1.apply(GridNearTransactionalCache.java:90)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
>
