You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gossip.apache.org by "Edward Capriolo (JIRA)" <ji...@apache.org> on 2017/08/01 01:31:00 UTC
[jira] [Updated] (GOSSIP-88) Data Replication Control
[ https://issues.apache.org/jira/browse/GOSSIP-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated GOSSIP-88:
----------------------------------
Fix Version/s: 0.1.3
> Data Replication Control
> ------------------------
>
> Key: GOSSIP-88
> URL: https://issues.apache.org/jira/browse/GOSSIP-88
> Project: Gossip
> Issue Type: New Feature
> Reporter: Mirage Abeysekara
> Assignee: Mirage Abeysekara
> Labels: gsoc2017
> Fix For: 0.1.3
>
>
> Currently shared data and per node data get replicated on all nodes. It is better to have data replication control with following requirements
> * Data should never get replicated
> * Data should only get replicated on given set of nodes
> * Data should only replicated on its Datacenter
> In implementation the AbstractActiveGossiper is currently sending its shared data and per node data to a randomly selected live member. To control this replication we add a new property to the message (eg: SharedDataMessage has a property which says whether this datum need to be replicated or not with a given member.) and use that property in the AbstractActiveGossiper when sending data to a member.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)