Hi Evan, I think this is an old property that isn't used anymore, so it would be good to clean it up and get rid of it.
Matei On Sep 28, 2013, at 6:23 PM, Evan Chan <[email protected]> wrote: > Hey guys, > > Does anyone see a reason to keep the "spark.hostPort" system property > around? > > It is cleared by lots of tests, set in two places (SparkEnv, and > StandaloneExecutorBackend), > and only used as follows: > > Utils.localHostPort() reads it > localHostPort is called from > - BlockManager (which calls it, but _never_ uses the resulting output!) > - MapOutputTracker (which passes it as a value, not sure to where) > > Just trying to clean house on properties. > > thanks, > Evan > > -- > -- > Evan Chan > Staff Engineer > [email protected] | > > <http://www.ooyala.com/> > <http://www.facebook.com/ooyala><http://www.linkedin.com/company/ooyala><http://www.twitter.com/ooyala>
