[
https://issues.apache.org/jira/browse/SPARK-27719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985270#comment-16985270
]
Jungtaek Lim commented on SPARK-27719:
--------------------------------------
If your application is streaming, I think we are going on the right approach to
deal with it - see https://issues.apache.org/jira/browse/SPARK-28594.
The point is, normally we don't want to stop reading event log until some
offset/size, as what we may really have interest is the "latest" status. And
there're some events which we shouldn't ignore or clean up - app start, app
end, environment update, etc.
> Set maxDisplayLogSize for spark history server
> ----------------------------------------------
>
> Key: SPARK-27719
> URL: https://issues.apache.org/jira/browse/SPARK-27719
> Project: Spark
> Issue Type: Improvement
> Components: Web UI
> Affects Versions: 3.0.0
> Reporter: hao.li
> Priority: Minor
>
> Sometimes a very large eventllog may be useless, and parses it may waste many
> resources.
> It may be useful to avoid parse large enventlogs by setting a configuration
> spark.history.fs.maxDisplayLogSize.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
