[
https://issues.apache.org/jira/browse/GOSSIP-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15842325#comment-15842325
]
ASF GitHub Bot commented on GOSSIP-39:
--------------------------------------
GitHub user edwardcapriolo opened a pull request:
https://github.com/apache/incubator-gossip/pull/28
GOSSIP-39 User Defined Active Gossip (review by Dorian Ellerbe)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/edwardcapriolo/incubator-gossip GOSSIP-39
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-gossip/pull/28.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 #28
----
commit 3f1882fbcf805f1b400411a2e1bd936784788f8c
Author: Edward Capriolo <[email protected]>
Date: 2017-01-23T02:32:18Z
GOSSIP-39 User Defined Active Gossip (review by Dorian Ellerbe)
----
> User controlled Gossip
> ----------------------
>
> Key: GOSSIP-39
> URL: https://issues.apache.org/jira/browse/GOSSIP-39
> Project: Gossip
> Issue Type: New Feature
> Reporter: Edward Capriolo
> Fix For: 0.1.2
>
>
> There are two interesting usecases:
> * Cassandra does this 'trick' where nodes gossip more often to seeds so that
> the cluster converges faster
> * It would be ideal if we could gossip more to some nodes than others. For
> example if we have a cluster in two data centers if they were more likely to
> gossip inside the wan
> The challenge here is flexibility vs complexity. Cassandra has a concept of
> Datacenter and Rack, do we make these 1st class parameters or do we let the
> logic consider ANY user data?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
