Ok got it figured out. LIBPROCESS_PORT is being unset along the way
somewhere by marathon/mesos, the solution was to start the spark driver
process via a script that re exports LIBPROCESS_PORT by reading it from a
var named something other than LIBPROCESS_PORT (in my case
SPARK_LIBPROCESS_PORT)
Can you set some other variable via the same mechanism and see if you can
see it in your app?
On Mon, May 19, 2014 at 10:54 AM, Scott Clasen sc...@heroku.com wrote:
hmm, I am setting it via the Environment passed in the REST call to create
the app, and if I look at the marathon UI I do see
Oh for sure, setting quite a few that I am seeing in the env.
On Mon, May 19, 2014 at 12:05 PM, Vinod Kone vinodk...@gmail.com wrote:
Can you set some other variable via the same mechanism and see if you can
see it in your app?
On Mon, May 19, 2014 at 10:54 AM, Scott Clasen
You can set LIBPROCESS_PORT in the environment.
On Wed, May 14, 2014 at 1:58 PM, Scott Clasen sc...@heroku.com wrote:
I raised this question on the Spark ML but it may be more a Mesos question.
I would like to be able to configure the port used to communicate between
the Mesos master and
Aha, thanks! I am still having an issue. I am executing the process via
marathon, with LIBPROCESS_PORT set in the env. However when I log the
value of LIBPROCESS_PORT in my program, I get 0.
Found a thread in this ML called
Re: Review Request: Unset LIBPROCESS_PORT before applying
5 matches
Mail list logo
