From b0fc922fafcf8fecc83e935c4792af19bf1f9c83 Mon Sep 17 00:00:00 2001 From: Joshi Date: Thu, 9 Jul 2015 16:30:14 -0700 Subject: [PATCH] History Server: updated order for multiple attempts(updated comment) --- .../org/apache/spark/deploy/history/FsHistoryProvider.scala | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala b/core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala index 698fb62620a01..250c38228ad7d 100644 --- a/core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala +++ b/core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala @@ -414,8 +414,7 @@ private[history] class FsHistoryProvider(conf: SparkConf, clock: Clock) /** * Comparison function that defines the sort order for application attempts within the same * application. Order is: completed attempts before running attempts, running attempts sorted - * by start time showing whichever started first, - * completed attempts sorted by end time showing whichever ended first. + * by ascending start time,completed attempts sorted by ascending end time. * * Normally applications should have a single running attempt; but failure to call sc.stop() * may cause multiple running attempts to show up.