You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:01:05 UTC
[jira] [Updated] (SPARK-20722) Replay event log that hasn't be
replayed in current checking period in advance for request
[ https://issues.apache.org/jira/browse/SPARK-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-20722:
---------------------------------
Labels: bulk-closed (was: )
> Replay event log that hasn't be replayed in current checking period in advance for request
> ------------------------------------------------------------------------------------------
>
> Key: SPARK-20722
> URL: https://issues.apache.org/jira/browse/SPARK-20722
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 2.1.1
> Reporter: sharkd tu
> Priority: Major
> Labels: bulk-closed
> Attachments: history-server1.png, history-server2.png
>
>
> History server may replay logs slowly if the size of event logs in current checking period is very large. It will get stuck for a while before entering next checking period, if we request a newer application history ui, we get the error like "Application application_1481785469354_934016 not found". We can let history server replay the newer event log in advance for request.
--
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