Mailing-List: contact dev-help@hama.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hama.apache.org
Date: Thu, 7 Mar 2013 08:00:16 +0000 (UTC)
From: "Thomas Jungblut (JIRA)" <jira@apache.org>
To: dev@hama.apache.org
Message-ID: <JIRA.12635698.1362618269675.398135.1362643216613@arcas>
In-Reply-To: <JIRA.12635698.1362618269675@arcas>
References: <JIRA.12635698.1362618269675@arcas>
Subject: [jira] [Commented] (HAMA-742) Implement of Hama RPC
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thomas Jungblut commented on HAMA-742:
--------------------------------------

Personally, I think the best solution would be to use RPC for our distributed system communication. And use a plain netty with Selectors (epoll) for our messaging system. RPC has too much overhead for message imho.
                
> Implement of Hama RPC 
> ----------------------
>
>                 Key: HAMA-742
>                 URL: https://issues.apache.org/jira/browse/HAMA-742
>             Project: Hama
>          Issue Type: Sub-task
>            Reporter: Edward J. Yoon
>             Fix For: 0.6.1
>
>
> To solve HDFS 2.0 compatibility issue, we have to change a lot of codes for Hadoop 2.0 RPC, moreover, yarn RPC doesn't support asynchronous call directly.
> Ultimately, we can pursue the performance and integrate more easily with hadoop multi-versions by having our own RPC.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira