Re: MTCGA: IGNITE-7791 and GridDhtPartitionsSingleMessage

Igniters, especially who participated in implementaion of IEP-4. I need your advice. I've prepeared fixes for this flaky test. Can you review my changes [1] and share your thoughts? In my opinion, we should not perform caches info removing from LocalJoinCachesContext captured state on reconnect

Re: MTCGA: IGNITE-7791 and GridDhtPartitionsSingleMessage

Hello Maxim, SingleMessage with exchId=null is sent when a node updates local partitions' state and schedules a background cluster notification. In contrast, when a partition map exchange happends, it is completed with exchId != null. I need more context regarding how this message interferes

Re: MTCGA: IGNITE-7791 and GridDhtPartitionsSingleMessage

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 г. в

Re: MTCGA: IGNITE-7791 and GridDhtPartitionsSingleMessage

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 : > Hi all, > > I'm working on [1] IgniteClientReconnectCacheTest

MTCGA: IGNITE-7791 and GridDhtPartitionsSingleMessage

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