Return-Path: X-Original-To: apmail-giraph-dev-archive@www.apache.org Delivered-To: apmail-giraph-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E707F90D4 for ; Mon, 25 Jun 2012 19:05:45 +0000 (UTC) Received: (qmail 37919 invoked by uid 500); 25 Jun 2012 19:05:45 -0000 Delivered-To: apmail-giraph-dev-archive@giraph.apache.org Received: (qmail 37858 invoked by uid 500); 25 Jun 2012 19:05:45 -0000 Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@giraph.apache.org Delivered-To: mailing list dev@giraph.apache.org Received: (qmail 37450 invoked by uid 500); 25 Jun 2012 19:05:45 -0000 Delivered-To: apmail-incubator-giraph-dev@incubator.apache.org Received: (qmail 37393 invoked by uid 99); 25 Jun 2012 19:05:45 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2012 19:05:45 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 9510914284C for ; Mon, 25 Jun 2012 19:05:44 +0000 (UTC) Date: Mon, 25 Jun 2012 19:05:44 +0000 (UTC) From: "Jakob Homan (JIRA)" To: giraph-dev@incubator.apache.org Message-ID: <815626999.52540.1340651144613.JavaMail.jiratomcat@issues-vm> In-Reply-To: <775210279.43525.1338987563052.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (GIRAPH-200) remove hadoop RPC and keep just netty MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/GIRAPH-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400786#comment-13400786 ] Jakob Homan commented on GIRAPH-200: ------------------------------------ If Giraph is going to run a secure cluster, it must also be secure. Running an unsecured Giraph opens up the possibility of a malicious party using it to grab data (vertices sent over the unsecured wire). If we don't have a security story, it's like that Giraph won't be allowed on any of secure clusters (from a policy standpoint). > 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: Remove_Hadoop_RPC_and_keep_just_Netty.patch, Remove_Hadoop_RPC_and_keep_just_Netty1.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