spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-22873) Init lastReportTimestamp with system current time when start() called in AsyncEventQueue
Date Sun, 28 Jan 2018 21:49:00 GMT

     [ 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


Mime
View raw message