Mailing-List: contact dev-help@spark.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@spark.apache.org
From: sryza <git@git.apache.org>
To: dev@spark.apache.org
Reply-To: dev@spark.apache.org
References: <git-pr-86-spark@git.apache.org>
In-Reply-To: <git-pr-86-spark@git.apache.org>
Subject: [GitHub] spark pull request: SPARK-1126. spark-app preliminary
Content-Type: text/plain
Message-Id: <20140307041440.119A293F198@tyr.zones.apache.org>
Date: Fri,  7 Mar 2014 04:14:39 +0000 (UTC)

Github user sryza commented on the pull request:

    https://github.com/apache/spark/pull/86#issuecomment-36966736
  
    I uploaded a new patch that doesn't start a new JVM and parses --driver-memory in bash. It wasn't as bad as I expected (thanks to some help from @umbrant and @atm).
    
    I've verified that it works with yarn with both deploy modes.  I'm still planning to add some tests and doc, but I wanted to upload it with the new approach in case there are any comments.


---
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.
---