-
- Downloads
SPARK-3574. Shuffle finish time always reported as -1
The included test waits 100 ms after job completion for task completion events to come in so it can verify they have reasonable finish times. Does anyone know a better way to wait on listener events that are expected to come in? Author: Sandy Ryza <sandy@cloudera.com> Closes #2440 from sryza/sandy-spark-3574 and squashes the following commits: c81439b [Sandy Ryza] Fix test failure b340956 [Sandy Ryza] SPARK-3574. Remove shuffleFinishTime metric
Showing
- core/src/main/scala/org/apache/spark/executor/TaskMetrics.scala 0 additions, 6 deletions...rc/main/scala/org/apache/spark/executor/TaskMetrics.scala
- core/src/main/scala/org/apache/spark/scheduler/JobLogger.scala 0 additions, 1 deletion...src/main/scala/org/apache/spark/scheduler/JobLogger.scala
- core/src/main/scala/org/apache/spark/util/JsonProtocol.scala 0 additions, 2 deletionscore/src/main/scala/org/apache/spark/util/JsonProtocol.scala
- core/src/test/scala/org/apache/spark/util/JsonProtocolSuite.scala 0 additions, 3 deletions.../test/scala/org/apache/spark/util/JsonProtocolSuite.scala
Loading
Please register or sign in to comment