[jira] [Resolved] (GOSSIP-88) Data Replication Control

[Edward Capriolo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GOSSIP-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Capriolo resolved GOSSIP-88.
---
Resolution: Fixed

Committed thanks! Great work!

> 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)

Re: Contribution(s) Agreement , IRC

[Edward Capriolo]

On Monday, July 31, 2017,  wrote:

> Hi Folks
>
> Wanted to check if we we need to get any contributions agreement signed
> off by the current employer for working on the project.
>
> Also do we plan to have an IRC channel setup
>
> Apologies if these has been answered before.
>
>
> Regards
> -jv


The apache software foundation does not require individual contributors
submitting patches to sign any specific agreements.

Submitting a pull request to the project implicitlity implies you are
contributing software to the ASF.

We can not answer questions about what your employer allows. You should
contact your employer if you believe an agreement you have would prevent
you from submitting code.

We have an irc room on freenode apach-gossip.


-- 
Sorry this was sent from mobile. Will do less grammar and spell check than
usual.

Contribution(s) Agreement , IRC

[juby . victor]

Hi Folks

Wanted to check if we we need to get any contributions agreement signed off by 
the current employer for working on the project. 

Also do we plan to have an IRC channel setup 

Apologies if these has been answered before. 


Regards
-jv

[REMINDER] Policies around Publicity & Press

[John D. Ament]

All Podlings,

In recent days I've been contacted about several publicity issues that have
gone a bit off kilter.  I wanted to remind podlings two very import
policies.

1. Podlings MUST coordinate with the Public Relations Committee with all
publicity activities.
2. The Press Team MUST review any press releases or similar communication
referencing a podling before it is published.

Relevant Links:

https://incubator.apache.org/guides/branding.html#publicity_activities
https://incubator.apache.org/guides/branding.html#publicity_throughout_the_incubation_process

Please reach out with any concerns.

Regards,

John D. Ament
VP, Apache Incubator

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

[Edward Capriolo (JIRA)]

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

Edward Capriolo commented on GOSSIP-35:
---

I assigned this issue to you [~jubyvictor]. Let me know how I can help if need 
be,.

> 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)

Re: Contribution to apache gossip

[Edward Capriolo]

On Sun, Jul 30, 2017 at 10:59 PM, Ankur Agrawal 
wrote:

> Hi
>
> Not sure if my previous email one week ago did actually get delivered. So I
> apologize for resenting in advance.
>
> My name is Ankur. I am a student, and I am keenly interested in, and want
> to contribute to this project for implementation of Gossip protocol.
>
> I have some job experience in designing instance migration services for a
> popular public cloud infrastructure, and distributed data backup and
> recovery services. I think this project will help me learn a lot, and I can
> also contribute while learning.
>
> I saw that GOSSIP-70 (https://issues.apache.org/jira/browse/GOSSIP-70) is
> still open. It was mentioned as a project in GSoC 2017 too. If this is
> indeed open, and you guys think I can start with this, it will be great.
> Please note that I am not participating in GSoC and I want to contribute on
> a individual capacity.
>
> If there are other open issues where you are looking for contribution too,
> do let me know, and I can get started with that.
>
> Also, I am wondering if there is any interest in implementation of Gossip
> in other languages like python or C++.
>
> I look forward to hear from you guys.
>
> Thanks
> Ankur
>

Thanks for your interest!

"Also, I am wondering if there is any interest in implementation of Gossip
in other languages like python or C++."

Originally we planned to port Gossip to multiple languages but there has
not been much interest in that. Currently the code base is evolving and
porting would be challenging. I think that is a lot for us to bite off at
this point.

GOSSIP-70 is a fine place to start. We have not fleshed that ticket out
enough. Starting a conversation in the ticket or on the mailing list would
be a good thing to do before we start coding. I like the idea of using a
formula to pick a quorum of nodes and doing an operation across them. This
can be easily extracted but we need to figure out what the first step is
and what a final target might be.

Thanks,
Edward