You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "ShuMing Li (JIRA)" <ji...@apache.org> on 2018/07/04 12:41:00 UTC

[jira] [Created] (SPARK-24738) [HistoryServer] FsHistoryProvider clean outdated event logs at start

ShuMing Li created SPARK-24738:
----------------------------------

             Summary: [HistoryServer] FsHistoryProvider clean outdated event logs at start	
                 Key: SPARK-24738
                 URL: https://issues.apache.org/jira/browse/SPARK-24738
             Project: Spark
          Issue Type: Bug
          Components: Spark Core
    Affects Versions: 2.3.1
            Reporter: ShuMing Li


Now FsHistoryProvider's policy :
 * 1. FsHistoryProvider create checkEvent thread and cleanLog thread, they share one thread pool to avoid conflicts;
 * 2. check thread replay all event logs first;
 * 3. clean thread iterators all events to check the outdated events and remove about it;

 

Why check thread at step2 not clean the outdated eventLogs at start, so no need replay the outdated logs to save times ?

 

```

// Used by check event thread and clean log thread.
// Scheduled thread pool size must be one, otherwise it will have concurrent issues about fs
// and applications between check task and clean task

```



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org