[
https://issues.apache.org/jira/browse/SPARK-22873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301021#comment-16301021
]
Apache Spark commented on SPARK-22873:
--------------------------------------
User 'Ngone51' has created a pull request for this issue:
https://github.com/apache/spark/pull/20053
> Init lastReportTimestamp with system current time when start() called in
> AsyncEventQueue
> ----------------------------------------------------------------------------------------
>
> Key: SPARK-22873
> URL: https://issues.apache.org/jira/browse/SPARK-22873
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 2.2.1
> Reporter: wuyi
> Priority: Minor
> Labels: newbie
>
> {code:java}
> if (droppedEventsCounter.compareAndSet(droppedCount, 0)) {
> val prevLastReportTimestamp = lastReportTimestamp
> lastReportTimestamp = System.currentTimeMillis()
> val previous = new java.util.Date(prevLastReportTimestamp)
> logWarning(s"Dropped $droppedEvents events from $name since $previous.")
> }
> {code}
> First time we log previous date, it would be "Thu Jan 01 08:00:00 CST 1970"
> because of lastReportTimestamp was inited by 0L. Although there is no mistake
> in theory, AsyncEventQueue's starting time seems better.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
