Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Mon, 6 Aug 2012 18:40:03 +0000 (UTC)
From: "Eugene Koontz (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <637932535.17769.1344278403070.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1534416787.17765.1344278283013.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (GIRAPH-282) Make netty the default RPC transport
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eugene Koontz updated GIRAPH-282:
---------------------------------

    Description: 
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.

  was:
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-211, so we need to simply break it out into a separate patch.

    
> Make netty the default RPC transport
> ------------------------------------
>
>                 Key: GIRAPH-282
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-282
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Eugene Koontz
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira