[
https://issues.apache.org/jira/browse/GOSSIP-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057975#comment-16057975
]
ASF GitHub Bot commented on GOSSIP-88:
--------------------------------------
GitHub user Mirage20 opened a pull request:
https://github.com/apache/incubator-gossip/pull/55
[WIP] GOSSIP-88 Data Replication Control
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mirage20/incubator-gossip GOSSIP-88
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-gossip/pull/55.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #55
----
commit 36d1cf04d048edb9ce24fd48cab7869231d53d99
Author: Miraj Abeysekara <[email protected]>
Date: 2017-06-21T18:19:39Z
sample replication control implementation
----
> 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
>
> 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)
