Return-Path: X-Original-To: apmail-incubator-giraph-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-giraph-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 A21C19E9C for ; Wed, 4 Apr 2012 18:47:40 +0000 (UTC) Received: (qmail 74965 invoked by uid 500); 4 Apr 2012 18:47:40 -0000 Delivered-To: apmail-incubator-giraph-dev-archive@incubator.apache.org Received: (qmail 74907 invoked by uid 500); 4 Apr 2012 18:47:40 -0000 Mailing-List: contact giraph-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: giraph-dev@incubator.apache.org Delivered-To: mailing list giraph-dev@incubator.apache.org Received: (qmail 74780 invoked by uid 99); 4 Apr 2012 18:47:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Apr 2012 18:47:40 +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; Wed, 04 Apr 2012 18:47:39 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 237A93582BF for ; Wed, 4 Apr 2012 18:47:19 +0000 (UTC) Date: Wed, 4 Apr 2012 18:47:19 +0000 (UTC) From: "Paolo Castagna (Commented) (JIRA)" To: giraph-dev@incubator.apache.org Message-ID: <1101810466.13290.1333565239154.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <759079618.23556.1321073811833.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (GIRAPH-77) Coordinator should expose a web interface with progress, vertex region assignments, etc. 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/GIRAPH-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246581#comment-13246581 ] Paolo Castagna commented on GIRAPH-77: -------------------------------------- Hi Avery, I am still learning and stepping into the Apache Giraph source code (fortunately, it isn't that big) :-) Do you or Jakob have a favorite stack to do that? Jetty/Netty?, JAX-RS?, etc. Any specific web framework and/or template engine? Something small, something to minimize dependencies, ... I tend to use Jetty with plain servlets and Velocity. But I am open to suggestions. Ideally, we could/should publish JSON and render HTML pages client side (once again, I accept suggestions on JavaScript frameworks). I must warn you though, I am not a web|graphic designer (and I know my limits on the UI front). But, once the basic functionalities are in place and the correct data is available, I am sure some good web designer will fix that up. Coming back to your question, with some guidance, yes. I would like to give it a shot and I have time to dedicate to Apache Giraph. > Coordinator should expose a web interface with progress, vertex region assignments, etc. > ---------------------------------------------------------------------------------------- > > Key: GIRAPH-77 > URL: https://issues.apache.org/jira/browse/GIRAPH-77 > Project: Giraph > Issue Type: New Feature > Reporter: Jakob Homan > > It would be nice if the coordinator worker had a web interface that showed progress, splits, etc. during job execution. Right now it would duplicate information currently being exposed through task status, but with the move to YARN, it will be a necessity. It would be great if we could do this in a modern way to avoid the screen-scraping, etc. currently used to get information from most other Hadoop project's web interfaces. The coordinator could announce its address at the beginning or via status updates. -- 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