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

Anton Vinogradov commented on IGNITE-9913:
------------------------------------------

Alexey Goncharuk,

1. Seems, I've got a situation, please check the understanding.

Prepared Txs can be located at backup nodes having partitions state from: 
{{[state == MOVING || state == OWNING || state == RENTING]}}
 So, we have to cover all these cases.
 For example, we should repair all partitions with non-finished rebalance 
(moving), correct?

So, {{Set<Integer> failedPrimaries = 
aff.primaryPartitions(fut.exchangeId().eventNode().id(), aff.lastVersion());}} 
is a correct calculation, but 
 {{Set<Integer> locBackups = 
aff.backupPartitions(fut.sharedContext().localNodeId(), aff.lastVersion());}} 
should be replaced with dht.localPartitions() usage?

> Prevent data updates blocking in case of backup BLT server node leave
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-9913
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9913
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Ivan Rakov
>            Assignee: Anton Vinogradov
>            Priority: Major
>             Fix For: 2.8
>
>         Attachments: 9913_yardstick.png, master_yardstick.png
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Ignite cluster performs distributed partition map exchange when any server 
> node leaves or joins the topology.
> Distributed PME blocks all updates and may take a long time. If all 
> partitions are assigned according to the baseline topology and server node 
> leaves, there's no actual need to perform distributed PME: every cluster node 
> is able to recalculate new affinity assigments and partition states locally. 
> If we'll implement such lightweight PME and handle mapping and lock requests 
> on new topology version correctly, updates won't be stopped (except updates 
> of partitions that lost their primary copy).



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

Reply via email to