[
https://issues.apache.org/jira/browse/FLINK-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656884#comment-15656884
]
ASF GitHub Bot commented on FLINK-5006:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2785
It's not about timing guarantees here, only about order of running timers.
The problem is that they are sorted by the delay which is affected by
races/stalls, rather than by proper timestamp.
Since Flink actually relies on timer triggering order, I think we need to
implement our own timer service, which sorts by actual timestamp, rather than
by delay.
> SystemProcessingTimeServiceTest.testTimerSorting fails
> ------------------------------------------------------
>
> Key: FLINK-5006
> URL: https://issues.apache.org/jira/browse/FLINK-5006
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Reporter: Ufuk Celebi
> Labels: test-stability
>
> {code}
> testTimerSorting(org.apache.flink.streaming.runtime.tasks.SystemProcessingTimeServiceTest)
> Time elapsed: 0.023 sec <<< FAILURE!
> java.lang.AssertionError: expected:<1478173518115> but was:<1478173518122>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at
> org.apache.flink.streaming.runtime.tasks.SystemProcessingTimeServiceTest.testTimerSorting(SystemProcessingTimeServiceTest.java:298)
> {code}
> Failed in a private branch with unrelated changes (the test is very much self
> contained).
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/172910645/log.txt
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
