Josh Rosen created SPARK-9026:
---------------------------------
Summary: SimpleFutureAction.onComplete should not tie up a
separate thread for each callback
Key: SPARK-9026
URL: https://issues.apache.org/jira/browse/SPARK-9026
Project: Spark
Issue Type: Bug
Components: Spark Core
Reporter: Josh Rosen
As [~zsxwing] points out at
https://github.com/apache/spark/pull/7276#issuecomment-121097747,
SimpleFutureAction currently blocks a separate execution context thread for
each callback registered via onComplete:
{code}
override def onComplete[U](func: (Try[T]) => U)(implicit executor:
ExecutionContext) {
executor.execute(new Runnable {
override def run() {
func(awaitResult())
}
})
}
{code}
We should fix this so that callbacks do not steal threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
