giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Avery Ching (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-282) Make netty the default RPC transport
Date Tue, 07 Aug 2012 00:42:03 GMT


Avery Ching commented on GIRAPH-282:

Are there any examples of anyone here who is still running HadoopRPC instead of Netty solely
due to security reasons?  

Frankly, there are other security holes mentioned by Eugene in GIRAPH-211 (i.e. ZooKeeper).
 I expect that we'll work through those issues when someone has time to get to them.  Does
this really need to block us from moving forward in the meantime?

We are holding up great code improvements (i.e. GIRAPH-200) and piling up cruft (see GIRAPH-45
if blocks on netty vs HadoopRPC).  Is there truly a great reason for this?
> Make netty the default RPC transport
> ------------------------------------
>                 Key: GIRAPH-282
>                 URL:
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Eugene Koontz
>            Assignee: Eugene Koontz
>         Attachments: GIRAPH-282.patch
> Currently we use Hadoop RPC as our means of communication amongst BSP workers, but we
would like to transition to Netty for its better performance. This would require making security
work by emulating Hadoop RPC's security features. See GIRAPH-211.
> The fix for this is present in Avery's GIRAPH-262 patch, so we need to simply break it
out into a separate patch.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message