spark-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Ash <>
Subject Re: Comprehensive Port Configuration reference?
Date Sun, 25 May 2014 23:24:27 GMT
Hi Jacob,

The config option spark.history.ui.port is new for 1.0  The problem that
History server solves is that in non-Standalone cluster deployment modes
(Mesos and YARN) there is no long-lived Spark Master that can store logs
and statistics about an application after it finishes.  History server is
the UI that renders logged data from applications after they complete.

Read more here: and

As far as the two vs four dynamic ports, are those all listening ports?  I
did observe 4 ports in use, but only two of them were listening.  The other
two were the random ports used for responses on outbound connections, the
source port of the (srcIP, srcPort, dstIP, dstPort) tuple that uniquely
identifies a TCP socket.

Thanks for taking a look through!

I also realized that I had a couple mistakes with the 0.9 to 1.0 transition
so appropriately documented those now as well in the updated PR.


On Fri, May 23, 2014 at 2:43 PM, Jacob Eisinger <> wrote:

> Howdy Andrew,
> I noticed you have a configuration item that we were not aware of:
> spark.history.ui.port .  Is that new for 1.0?
> Also, we noticed that the Workers and the Drivers were opening up four
> dynamic ports per application context.  It looks like you were seeing two.
> Everything else looks like it aligns!
> Jacob
> Jacob D. Eisinger
> IBM Emerging Technologies
> - (512) 286-6075
> [image: Inactive hide details for Andrew Ash ---05/23/2014 10:30:58
> AM---Hi everyone, I've also been interested in better understanding]Andrew
> Ash ---05/23/2014 10:30:58 AM---Hi everyone, I've also been interested in
> better understanding what ports are used where
> From: Andrew Ash <>
> To:
> Date: 05/23/2014 10:30 AM
> Subject: Re: Comprehensive Port Configuration reference?
> ------------------------------
> Hi everyone,
> I've also been interested in better understanding what ports are used
> where and the direction the network connections go.  I've observed a
> running cluster and read through code, and came up with the below
> documentation addition.
> **<>
> Scott and Jacob -- it sounds like you two have pulled together some of
> this yourselves for writing firewall rules.  Would you mind taking a look
> at this pull request and confirming that it matches your observations?
>  Wrong documentation is worse than no documentation, so I'd like to make
> sure this is right.
> Cheers,
> Andrew
> On Wed, May 7, 2014 at 10:19 AM, Mark Baker <**<>>
> wrote:
>    On Tue, May 6, 2014 at 9:09 AM, Jacob Eisinger <**<>>
>    wrote:
>    > In a nut shell, Spark opens up a couple of well known ports.
>     And,then the workers and the shell open up dynamic ports for each job.
>     These dynamic ports make securing the Spark network difficult.
>    Indeed.
>    Judging by the frequency with which this topic arises, this is a
>    concern for many (myself included).
>    I couldn't find anything in JIRA about it, but I'm curious to know
>    whether the Spark team considers this a problem in need of a fix?
>    Mark.

View raw message