Return-Path: X-Original-To: apmail-hama-dev-archive@www.apache.org Delivered-To: apmail-hama-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 3CC2210BB3 for ; Wed, 27 Nov 2013 16:16:36 +0000 (UTC) Received: (qmail 38343 invoked by uid 500); 27 Nov 2013 16:16:36 -0000 Delivered-To: apmail-hama-dev-archive@hama.apache.org Received: (qmail 38256 invoked by uid 500); 27 Nov 2013 16:16:35 -0000 Mailing-List: contact dev-help@hama.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hama.apache.org Delivered-To: mailing list dev@hama.apache.org Received: (qmail 38247 invoked by uid 99); 27 Nov 2013 16:16:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Nov 2013 16:16:35 +0000 Date: Wed, 27 Nov 2013 16:16:35 +0000 (UTC) From: "Renil J (JIRA)" To: dev@hama.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HAMA-637) Implement Group membership API for tasks 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/HAMA-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833908#comment-13833908 ] Renil J commented on HAMA-637: ------------------------------ Hi Suraj,Nice to meet you. Yes, I have been trying to understand this feature and implement it.I'll post a design doc and patch on this jira as soon as I'm ready to present the details.Can you suggest me with some ways to test this implementation. Thanks > Implement Group membership API for tasks > ---------------------------------------- > > Key: HAMA-637 > URL: https://issues.apache.org/jira/browse/HAMA-637 > Project: Hama > Issue Type: New Feature > Components: bsp core > Reporter: Suraj Menon > Assignee: Renil J > > We should experiment the effectiveness of this feature. Instead of a peer sending message to each of the peers that logically a part of a group(active vertices of graph, members of group in a cluster, etc.) > The API could be: > {code} > peer.sendMessageToGroup(String group, Writable message); > {code} > This should result in finding all the peers that are members of that group and send message to each of the peers in the group. > Peers can change their membership status using the following API. > The guarantee of the group membership is ensured only in the next superstep. > {code} > peer.registerWithGroup(String group, Writable message); > peer.deregisterFromGroup(String group, Writable message); > {code} > For now we can try using Zookeeper for this solution. -- This message was sent by Atlassian JIRA (v6.1#6144)