[
https://issues.apache.org/jira/browse/SPARK-24787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583964#comment-16583964
]
Sanket Reddy commented on SPARK-24787:
--------------------------------------
Thanks [~ste...@apache.org] [~vanzin] [~tgraves] it seems we might have to
stick with hflush but think of potentially another solution to update the file
status changes similar to YARN ATS.
Even if I periodically update it I think the dropped events issue might persist
as it hard to have a proper flow control.
> Events being dropped at an alarming rate due to hsync being slow for
> eventLogging
> ---------------------------------------------------------------------------------
>
> Key: SPARK-24787
> URL: https://issues.apache.org/jira/browse/SPARK-24787
> Project: Spark
> Issue Type: Bug
> Components: Spark Core, Web UI
> Affects Versions: 2.3.0, 2.3.1
> Reporter: Sanket Reddy
> Priority: Minor
>
> [https://github.com/apache/spark/pull/16924/files] updates the length of the
> inprogress files allowing history server being responsive.
> Although we have a production job that has 60000 tasks per stage and due to
> hsync being slow it starts dropping events and the history server has wrong
> stats due to events being dropped.
> A viable solution is not to make it sync very frequently or make it
> configurable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
