Aaron Davidson 432201c7ee SPARK-1582 Invoke Thread.interrupt() when cancelling jobs ... Sometimes executor threads are blocked waiting for IO or monitors, and the current implementation of job cancellation may never recover these threads. By simply invoking Thread.interrupt() during cancellation, we can often safely unblock the threads and use them for subsequent work. Note that this feature must remain optional for now because of a bug in HDFS where Thread.interrupt() may cause nodes to be marked as permanently dead (as the InterruptedException is reinterpreted as an IOException during communication with some node). Author: Aaron Davidson <aaron@databricks.com> Closes #498 from aarondav/cancel and squashes the following commits: e52b829 [Aaron Davidson] Don't use job.properties when null 82f78bb [Aaron Davidson] Update DAGSchedulerSuite b67f472 [Aaron Davidson] Add comment on why interruptOnCancel is in setJobGroup 4cb9fd6 [Aaron Davidson] SPARK-1582 Invoke Thread.interrupt() when cancelling jobs		2014-04-23 16:52:49 -07:00
..
src	SPARK-1582 Invoke Thread.interrupt() when cancelling jobs	2014-04-23 16:52:49 -07:00
pom.xml	[SPARK-1560]: Updated Pyrolite Dependency to be Java 6 compatible	2014-04-22 09:44:41 -07:00