-
- Downloads
Fix createActorSystem not actually using the systemName parameter.
This meant all system names were "spark", which worked, but didn't lead to the most intuitive log output. This fixes createActorSystem to use the passed system name, and refactors Master/Worker to encapsulate their system/actor names instead of having the clients guess at them. Note that the driver system name, "spark", is left as is, and is still repeated a few times, but that seems like a separate issue.
Showing
- core/src/main/scala/spark/deploy/LocalSparkCluster.scala 13 additions, 25 deletionscore/src/main/scala/spark/deploy/LocalSparkCluster.scala
- core/src/main/scala/spark/deploy/client/Client.scala 3 additions, 10 deletionscore/src/main/scala/spark/deploy/client/Client.scala
- core/src/main/scala/spark/deploy/master/Master.scala 21 additions, 3 deletionscore/src/main/scala/spark/deploy/master/Master.scala
- core/src/main/scala/spark/deploy/worker/Worker.scala 26 additions, 32 deletionscore/src/main/scala/spark/deploy/worker/Worker.scala
- core/src/main/scala/spark/storage/BlockManagerMaster.scala 0 additions, 2 deletionscore/src/main/scala/spark/storage/BlockManagerMaster.scala
- core/src/main/scala/spark/util/AkkaUtils.scala 5 additions, 1 deletioncore/src/main/scala/spark/util/AkkaUtils.scala
Loading
Please register or sign in to comment