You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gossip.apache.org by "Juby Victor (JIRA)" <ji...@apache.org> on 2017/08/02 03:55:00 UTC

[jira] [Commented] (GOSSIP-35) Different payloads can be transmitted at different rates

    [ https://issues.apache.org/jira/browse/GOSSIP-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110241#comment-16110241 ] 

Juby Victor commented on GOSSIP-35:
-----------------------------------

Thanks Edward, I just started going over the codebase. Looks like the changes need to be done on GossipSettings and has side effects on gossip-base/SimpleActiveGossipper#init and gossip-transport/UdpTransportManager. 

I'm thinking of introducing 5 new params 

* deadMemberGossipInterval
* aliveMemberGossipInterval
* perNodeDataGossipInterval
* sharedDataGossipInterval

* udpSocketTimeoutInterval 

Should we support overriding these properties via environment variables ? 

> Different payloads can be transmitted at different rates
> --------------------------------------------------------
>
>                 Key: GOSSIP-35
>                 URL: https://issues.apache.org/jira/browse/GOSSIP-35
>             Project: Gossip
>          Issue Type: New Feature
>            Reporter: Edward Capriolo
>            Assignee: Juby Victor
>             Fix For: 0.1.3
>
>
> Current we have a a few ScheduledExectuor one that controls active gossip, one that controls gossip to dead nodes, one that controls gosssip of user data, etc. Currently they all use the same setting to control how often they run (10ms currently). It would be better if they each had their own setting. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)