[IGNITE-13302] Java thin client connect/disconnect during topology update may lead to partition divergence in ignite-sys-cache

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.10, 2.9.1
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Stepachev Maksim
• Reporter: Stepachev Maksim
• Created: 27/Jul/20 12:28
• Updated: 30/Nov/20 14:06
• Resolved: 05/Aug/20 21:07

Description

And you can see partition inconsistency in ignite-sys-cache

[2020-04-23 15:26:31,816][WARN ][sys-#45%gridgain.Sdsb11784Ver20%][root] Partition states validation has failed for group: ignite-sys-cache, msg: Partitions cache sizes are inconsistent for Part 31: [127.0.0.1:47500=1 127.0.0.1:47501=2 ] Part 43: [127.0.0.1:47500=3 127.0.0.1:47501=4 ] Part 44: [127.0.0.1:47500=1 127.0.0.1:47501=2 ] Part 46: [127.0.0.1:47500=0 127.0.0.1:47501=1 ] Part 91: [127.0.0.1:47500=1 127.0.0.1:47501=2 ]

Research results: 

Entries with an internal key type doesn't check in differed delete queue, it leads to inconsistency. 

Issue Links

• links to: GitHub Pull Request #8096