{"push_id":666478256,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ff71d34e00b64d70f671f9bf3e63aec39cd525e5","before":"2f22424e9f6624097b292cb70e00787b69d80718","commits":[{"sha":"ff71d34e00b64d70f671f9bf3e63aec39cd525e5","author":{"email":"5d14e010a5b345b784fd604efcc6cebb79f97468@gmail.com","name":"zsxwing"},"message":"[SPARK-7693][Core] Remove \"import scala.concurrent.ExecutionContext.Implicits.global\"\n\nLearnt a lesson from SPARK-7655: Spark should avoid to use `scala.concurrent.ExecutionContext.Implicits.global` because the user may submit blocking actions to `scala.concurrent.ExecutionContext.Implicits.global` and exhaust all threads in it. This could crash Spark. So Spark should always use its own thread pools for safety.\n\nThis PR removes all usages of `scala.concurrent.ExecutionContext.Implicits.global` and uses proper thread pools to replace them.\n\nAuthor: zsxwing <zsxwing@gmail.com>\n\nCloses #6223 from zsxwing/SPARK-7693 and squashes the following commits:\n\na33ff06 [zsxwing] Decrease the max thread number from 1024 to 128\ncf4b3fc [zsxwing] Remove \"import scala.concurrent.ExecutionContext.Implicits.global\"","distinct":true,"url":"https://api.github.com/repos/apache/spark/commits/ff71d34e00b64d70f671f9bf3e63aec39cd525e5"}]}