giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Reisman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-200) remove hadoop RPC and keep just netty
Date Fri, 06 Jul 2012 16:19:35 GMT

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

Eli Reisman commented on GIRAPH-200:
------------------------------------

I have not looked into the security aspects of Giraph much yet but isn' the hadoop/ stuff
(BspTokenSelector etc) for dealing with delegation tokens? maybe we can use that as a model
to set up security for Netty and then ditch it? My feeble understanding about the security
situation is that we need to interact with Hadoop security at the delegation token level?
Or since we have our own RPC system now, do we need to worry about encrypting the exchanges
of vertices/partitions across the wire whenever we dynamically repartition etc. ? 

                
> remove hadoop RPC and keep just netty
> -------------------------------------
>
>                 Key: GIRAPH-200
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-200
>             Project: Giraph
>          Issue Type: Improvement
>    Affects Versions: 0.2.0
>            Reporter: Claudio Martella
>            Assignee: Alessandro Presta
>             Fix For: 0.2.0
>
>         Attachments: GIRAPH-200.patch, GIRAPH-200.patch, GIRAPH-200.patch
>
>
> Given the netty communication behaves faster than rpc, we should just keep netty-based
and drop the older one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message