You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Rakov (JIRA)" <ji...@apache.org> on 2018/10/17 13:20:00 UTC
[jira] [Updated] (IGNITE-9913) Prevent data updates blocking in
case of backup BLT server node leave
[ https://issues.apache.org/jira/browse/IGNITE-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Rakov updated IGNITE-9913:
-------------------------------
Description:
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).
was:
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 on server node leave (except updates of partitions that lost their primary copy).
> 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: Ivan Rakov
> Priority: Major
> Fix For: 2.8
>
>
> 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
(v7.6.3#76005)