[
https://issues.apache.org/jira/browse/IGNITE-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993233#comment-16993233
]
Anton Vinogradov commented on IGNITE-9913:
------------------------------------------
[~ascherbakov]
>> for this exchange forceAffReassignment=true and
>> GridDhtPartitionsFullMessage#idealAffinityDiff().isEmpty()
Unfortunatelly idealAffinityDiff().isEmpty() does not mean cluster rebalanced,
it only shows primaries are rebalanced.
It rebalanced when we have empty waitinfo which calculated only at coordinator.
So, it seems, the flag is required.
>> Can we get rid of sending any assignments for protocol v3 ?
It seems it's possible, will check.
>> Also could you add a test ...
Sure
> 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
> Attachments: 9913_yardstick.png, master_yardstick.png
>
> Time Spent: 9h 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)
