You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Sergey Chugunov (JIRA)" <ji...@apache.org> on 2017/12/20 10:41:00 UTC
[jira] [Created] (IGNITE-7258) BinaryMetadata may be lost if node
with outdated metadata becomes a coordinator
Sergey Chugunov created IGNITE-7258:
---------------------------------------
Summary: BinaryMetadata may be lost if node with outdated metadata becomes a coordinator
Key: IGNITE-7258
URL: https://issues.apache.org/jira/browse/IGNITE-7258
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
Priority: Critical
Fix For: 2.4
Consider the following scenario in PDS-enabled mode:
# Multinode cluster is up and running, BinaryMetadata for some type is created and spread across all nodes.
# Node#1 leaves the cluster, then BinaryMetadata is updated one more time.
# All cluster is restarted *and Node#1 becomes a coordinator*.
As in current implementation coordinator is considered to own a master copy of BinaryMetadata, it spreads its out-of-date version to all nodes so update from step#2 is lost.
We need to improve BinaryMetadata exchange protocol so nodes on join will send their version of BinaryMetadata to coordinator so it is able to update its own local version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)