Return-Path: X-Original-To: apmail-incubator-hama-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-hama-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 258666963 for ; Tue, 12 Jul 2011 10:56:31 +0000 (UTC) Received: (qmail 2309 invoked by uid 500); 12 Jul 2011 10:56:30 -0000 Delivered-To: apmail-incubator-hama-dev-archive@incubator.apache.org Received: (qmail 2211 invoked by uid 500); 12 Jul 2011 10:56:26 -0000 Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hama-dev@incubator.apache.org Delivered-To: mailing list hama-dev@incubator.apache.org Received: (qmail 2198 invoked by uid 99); 12 Jul 2011 10:56:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jul 2011 10:56:23 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jul 2011 10:56:21 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id C7EA74B8FC for ; Tue, 12 Jul 2011 10:55:59 +0000 (UTC) Date: Tue, 12 Jul 2011 10:55:59 +0000 (UTC) From: "ChiaHung Lin (JIRA)" To: hama-dev@incubator.apache.org Message-ID: <1188285595.5561.1310468159815.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1875145306.10034.1299735119411.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HAMA-363) Add network condition monitoring function to BSPMaster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HAMA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063815#comment-13063815 ] ChiaHung Lin commented on HAMA-363: ----------------------------------- My test on my current vms looks work. But after reading parts of the paper[1], I discover the current implementation lacks of features such as federation, data transport, etc. The federation can provide aggregative information so that e.g. BSPMaster can proceed further by deciding if a worker fails, which is required by monitor service. In addition, plugin part may probably need to be improved as well, though at the moment from the developer's viewpoint it looks ok. [1]. The ganglia distributed monitoring system: design, implementation, and experience. http://ganglia.info/papers/science.pdf > Add network condition monitoring function to BSPMaster > ------------------------------------------------------ > > Key: HAMA-363 > URL: https://issues.apache.org/jira/browse/HAMA-363 > Project: Hama > Issue Type: New Feature > Components: bsp > Affects Versions: 0.3.0 > Reporter: Edward J. Yoon > Fix For: 0.4.0 > > Attachments: HAMA-363.patch, HAMA-363.patch, HAMA-363.patch > > > There's few reason why this issue is important. Basically Master server should know the status of cluster: > * to optimize the network usage > * to handle network connectivity problems > * to handle different network conditions > And, I would like to see some network usage statistics. > In this issue, we implement only basic function which is collect network usage. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira