[
https://issues.apache.org/jira/browse/IGNITE-13302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171758#comment-17171758
]
Vyacheslav Koptilin commented on IGNITE-13302:
----------------------------------------------
Hello [~mstepachev],
The fix looks good to me. Thank you for your efforts!
> Java thin client connect/disconnect during topology update may lead to
> partition divergence in ignite-sys-cache
> ---------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-13302
> URL: https://issues.apache.org/jira/browse/IGNITE-13302
> Project: Ignite
> Issue Type: Bug
> Reporter: Stepachev Maksim
> Assignee: Stepachev Maksim
> Priority: Major
> Fix For: 2.10
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> And you can see partition inconsistency in ignite-sys-cache
> {noformat}
> [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 ]
> {noformat}
> Research results:
> Entries with an internal key type doesn't check in differed delete queue, it
> leads to inconsistency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
