[jira] [Commented] (IGNITE-15364) The rebalancing can be broken if historical rebalancing is reassigned after the client node joined the cluster.

["Ignite TC Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-15364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410540#comment-17410540 ] 

Ignite TC Bot commented on IGNITE-15364:
----------------------------------------

{panel:title=Branch: [pull/9352/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9352/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}PDS (Indexing){color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=6166875]]
* {color:#013220}IgnitePdsWithIndexingCoreTestSuite: IgniteWalRebalanceTest.testSwitchHistoricalRebalanceToFullAndClientWithCacheJoin - PASSED{color}

{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=6166907&buildTypeId=IgniteTests24Java8_RunAll]

> The rebalancing can be broken if historical rebalancing is reassigned after the client node joined the cluster.
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-15364
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15364
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vyacheslav Koptilin
>            Assignee: Vyacheslav Koptilin
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Looks like the following scenario can break data consistency after rebalancing:
>  - start and activate the cluster of three server nodes
>  - create a cache with two backups and fill initial data into it
>  - stop one server node and upload additional data to the cache in order to trigger historical rebalance after the node returns to the cluster
>  - restart the node. make sure that historical rebalancing is started from two other nodes.
>  - before rebalancing is completed a new client node should be started and joined the cluster. this leads to clean up partition update counters on server nodes, i.e. _GridDhtPartitionTopologyImpl#cntrMap_. ( * )
>  - historical rebalancing from one node fails.
>  - in that case, rebalancing is reassigned and starting node tries to rebalance missed partitions from another node.
> unfortunately, update counters for historical rebalance cannot be properly calculated due to ( * )



--
This message was sent by Atlassian Jira
(v8.3.4#803005)