You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2018/01/28 21:49:00 UTC
[jira] [Resolved] (SPARK-22873) Init lastReportTimestamp with
system current time when start() called in AsyncEventQueue
[ https://issues.apache.org/jira/browse/SPARK-22873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-22873.
-------------------------------
Resolution: Not A Problem
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org