reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Seokchan Ahn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-362) Implement a Wake Transport using HTTP
Date Tue, 21 Mar 2017 17:05:41 GMT

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

Seokchan Ahn commented on REEF-362:
-----------------------------------

Hi,
I am an undergraduate student of Computer Science & Engineering, Seoul National University,
Korea.
Recently, I have started working on the project that uses hadoop and spark. I am very interested
in the subject of scheduling in a distributed system.
HTTP(S) seems also necessary for Wake and I would like to work to support this protocol.

> Implement a Wake Transport using HTTP
> -------------------------------------
>
>                 Key: REEF-362
>                 URL: https://issues.apache.org/jira/browse/REEF-362
>             Project: REEF
>          Issue Type: Improvement
>          Components: Wake, Wake.NET
>            Reporter: Markus Weimer
>              Labels: GSoC, gsoc2017
>
> Wake currently uses TCP connections for its messages. This is fast and efficient, but
provides challenges in some network environments. Also, it is considerable work to support
authentication and encryption.
> We could provide HTTP(S) as an alternative protocol for Wake. This transport will likely
be less efficient than the current path, but gain in security. And for the relatively small
messages used by the REEF control flow, the trade-off is likely worth it.



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

Mime
View raw message