Mailing-List: contact dev-help@spark.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@spark.apache.org
From: pwendell <git@git.apache.org>
To: dev@spark.apache.org
Reply-To: dev@spark.apache.org
References: <git-pr-42-spark@git.apache.org>
In-Reply-To: <git-pr-42-spark@git.apache.org>
Subject: [GitHub] spark pull request: [WIP] [SPARK-1132] Persisting Web UI
 through r...
Content-Type: text/plain
Message-Id: <20140304204148.B12E4935EBB@tyr.zones.apache.org>
Date: Tue,  4 Mar 2014 20:41:48 +0000 (UTC)

Github user pwendell commented on a diff in the pull request:

    https://github.com/apache/spark/pull/42#discussion_r10273534
  
    --- Diff: core/src/main/scala/org/apache/spark/ui/UIReloader.scala ---
    @@ -0,0 +1,46 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one or more
    + * contributor license agreements.  See the NOTICE file distributed with
    + * this work for additional information regarding copyright ownership.
    + * The ASF licenses this file to You under the Apache License, Version 2.0
    + * (the "License"); you may not use this file except in compliance with
    + * the License.  You may obtain a copy of the License at
    + *
    + *    http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +
    +package org.apache.spark.ui
    +
    +/**
    + * Reload a persisted UI independently from a SparkContext
    + */
    +object UIReloader {
    --- End diff --
    
    We should think a bit about the right way to expose the "rebuild a UI" logic inside of Spark. The first goal here is that the existing standalone cluster manager should, once an application completes, be able to re-render the existing UI for that application. The ideal semantics would be that you can just point to a directory in HDFS known to contain the logs and have it add new handlers to an existing jetty server. Right now the SparkUI starts its own server always so that might need to be altered. 
    
    A second goal is to have simple standalone version that can run in it's own JVM that basically "watches" a base directory and reports new applications as they arrive. This one would also need to create multiple SparkUI's in the same JVM.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---