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

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

[~agoncharuk]
 Thanks for joining!

1. Not sure I've got an issue.
 As far as I can see {{aff.[primary,backup]Partitions}} uses {{aff.assignment}} 
(not an {{idealAssignment}}) to calculate list of nodes.
 Having that baseline enabled and was not changed we should just check the 
latest assignment, which was calculated using part2node during the latest 
finished regular PME.
 Have I missed something? Could you, please, reexplain the situation?

2. Non-affected nodes finish PME immediately. 
 So, we will block new operations only at affected nodes and only during the 
recovery.
 Benchmarks are in progress, will provide the result once it will be ready.
 But the main improvement here should be the ability to skip waiting for 
already started operations completion.

> 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