You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spark.apache.org by Jacek Laskowski <ja...@japila.pl> on 2016/05/06 07:36:24 UTC
TaskSchedulerImpl#initialize - why is rootPool initialized here not
while TaskSchedulerImpl is created?
Hi,
While reviewing TaskSchedulerImpl I've noticed that rootPool is
created and initialized in TaskSchedulerImpl#initialize [1], but seems
legit to do it as part of TaskSchedulerImpl's instantiation.
What is the reason for creating and initializing rootPool late in
TaskSchedulerImpl's lifecycle?
[1] https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala#L131-L142
Pozdrawiam,
Jacek Laskowski
----
https://medium.com/@jaceklaskowski/
Mastering Apache Spark http://bit.ly/mastering-apache-spark
Follow me at https://twitter.com/jaceklaskowski
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
For additional commands, e-mail: dev-help@spark.apache.org