Return-Path: X-Original-To: apmail-crunch-dev-archive@www.apache.org Delivered-To: apmail-crunch-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 3D38BD2D8 for ; Wed, 27 Feb 2013 07:30:51 +0000 (UTC) Received: (qmail 25448 invoked by uid 500); 27 Feb 2013 07:30:51 -0000 Delivered-To: apmail-crunch-dev-archive@crunch.apache.org Received: (qmail 25370 invoked by uid 500); 27 Feb 2013 07:30:50 -0000 Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@crunch.apache.org Delivered-To: mailing list dev@crunch.apache.org Received: (qmail 25342 invoked by uid 99); 27 Feb 2013 07:30:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 07:30:49 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.227.126.171] (HELO moutng.kundenserver.de) (212.227.126.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 07:30:40 +0000 Received: from mafr.de (et-1-41.gw-nat.bs.ka.oneandone.net [212.227.66.11]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MJmWC-1U9V0H3gMW-001Igt; Wed, 27 Feb 2013 08:30:09 +0100 Date: Wed, 27 Feb 2013 08:30:07 +0100 From: Matthias Friedrich To: dev@crunch.apache.org Subject: Re: About status web page Message-ID: <20130227073007.GA4998@mafr.de> Mail-Followup-To: dev@crunch.apache.org References: <20130226183041.GA18293@mafr.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V02:K0:XKjDLYoj1M3mZXEgDXtBA3JUdxYtos9L+d7KmJEYlD5 Y5zsl8DUTV+08UM/gdGLoNupE6ZuJaTDRoiejROGM1rpDWKWuJ lUelJlzD8tNu2AbQGBqqTOkuCmG+SLfsPICaZIYn3zuJ0JS1eE qzihlLGq8HwPqSJoz3pg8MNWEK29D1RFczNxQ6C0eO9wNuQh3r o3z6ZcvPWWvbvdJ4l9Onyk9ynArj1iYc0hbRNWcLBWBkxFc8Y1 av/9tYN6B72LrZyTsMMoAV9a/63yATmHSyVYDeZg8EQExZ7Doy i62n2+6mm+I8oeuJwt8d3BID0KKKado/uqlpZ/mUq0R/MbwMnG 6icaBhG8oUR2PE15FlOw= X-Virus-Checked: Checked by ClamAV on apache.org On Wednesday, 2013-02-27, Chao Shi wrote: > I'm developing a complex pipeline (30+ MRs plus lots of joins). I have a > hard time to understand which part of the pipeline spends most running time > and how much intermediate output does it produce. Crunch's optimization > work is great, but it makes the execution plan difficult to be understood. > Each time I modified the pipeline, I have to dump the dot file and run > graphviz to generate a new picture and examine if there's anything wrong. > > About security, I'm not familiar with how Hadoop does it. I will try to > reuse hadoop's HttpServer (does it have something to do with security?). > The bottom line is to make this feature disabled by default, and let users > enable it at their own risk. OK, sounds good. > If this feature is enabled, the user can choose to use unused port or > specified port. I haven't got an idea that how the user know the randomly > picked port (via log?) . I will be working on a prototype version first, > and see if the status page is generally useful. Yeah, logging the URL would probably be the only thing that works. Not counting fancy stuff like MDNS ;-) In my opinion, we should try to get this done with the dependencies that we already get through Hadoop. Each additional library we add to Crunch will cause interoperability problems for someone. Regards, Matthias