Hi Maxim, I didn't know answer, so I decided to provide at least general intro information. I hope it would be useful for you and for newcomers.
https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood Sincerely, Dmitriy Pavlov вт, 13 мар. 2018 г. в 21:28, Dmitry Pavlov <dpavlov....@gmail.com>: > Hi Alexey, > > Could you help with this question? > > I've observed such messages, it were probably sent by timeout, but not > sure their purpose. > > Sincerely, > Dmitriy Pavlov > > вт, 13 мар. 2018 г. в 20:58, Maxim Muzafarov <maxmu...@gmail.com>: > >> Hi all, >> >> I'm working on [1] IgniteClientReconnectCacheTest class with frakly >> test-case testReconnectCacheDestroyedAndCreated with success rate 32.4%. >> >> I've leaved comment in JIRA [2] and new test-case with reproducing this >> issue. >> Basicly, when we receiving GridDhtPartitionsSingleMessage with >> exchId=null not >> in proper time we've got this Assertion error. Ignite client instance >> erases all it's caches after reconnect, so it has no information about >> cache named 'static-cache' that persists on server nodes and when he >> recieve this SignleMessage after reconnection it will have 'Failed to >> reinitialize local partitions (preloading will be stopped)'. >> >> Should we perform clean-up [3] client caches in case of reconnect client >> ignite instance? >> Why we should clean clinent caches after node reconnects? Can't catch the >> idea of it. >> >> [1] https://issues.apache.org/jira/browse/IGNITE-7791 >> [2] >> >> https://issues.apache.org/jira/browse/IGNITE-7791?focusedCommentId=16391409&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16391409 >> [3] >> >> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/CacheAffinitySharedManager.java#L190 >> >
