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 mcenrue (JIRA)" <ji...@apache.org> on 2017/03/10 04:33:38 UTC

[jira] [Comment Edited] (GOSSIP-51) Consider alternative consensus based protocols

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

edward mcenrue edited comment on GOSSIP-51 at 3/10/17 4:32 AM:
---------------------------------------------------------------

Hi, I'm Edward McEnrue, and I was wondering how I could get in touch with you to discuss SWIM's pros and cons to elaborate on in the proposal? My capstone team in my undergraduate education implemented SWIM w/ java and tested it on AWS, so I do believe I could be of assistance for GSOC-2017. Thank you for the opportunity. My email is edward.mcenrue@gmail.com


was (Author: emcenrue):
Hi, I'm Edward McEnrue, and I was wondering how I could get in touch with you to discuss SWIM's pros and cons to elaborate on in the proposal? My capstone team in my undergraduate education implemented SWIM w/ java and tested it on AWS, so I do believe I could be of assistance for GSOC-2017. Thank you for the opportunity.

> Consider alternative consensus based protocols
> ----------------------------------------------
>
>                 Key: GOSSIP-51
>                 URL: https://issues.apache.org/jira/browse/GOSSIP-51
>             Project: Gossip
>          Issue Type: New Feature
>            Reporter: Edward Capriolo
>              Labels: gsoc2017
>
> Currently Gossip uses an ActiveThread to broadcast state. We should consider other protocols in such a way that the user can chose what works.
> SWIM is one alternative
> https://www.cs.cornell.edu/~asdas/research/dsn02-swim.pdf
> The goal of this issue would be to build a second consensus 'system' for gossip.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)