On a related note, there are tons of spark.akka.* properties. Does anyone see why we should not just use the base akka.* properties defined by Akka itself? Right now the code simply maps spark.akka.* to akka.* when starting Akka.
The only reasons I see for keeping spark.akka is that we might not want people fiddling with the base Akka properties. On the other hand, Akka's documentation is excellent, and using akka's own config properties means we no longer need to keep up with this shim layer. -Evan On Sat, Sep 28, 2013 at 3:44 PM, Matei Zaharia <[email protected]>wrote: > 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> > > -- -- 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>
