Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/2785
@StephanEwen I think it's not a problem that these physical, low-level
timers don't fire in order of their timestamp because the ordering of timers is
maintained in the implementation of `InternalTimerService` (in a queue in the
current implementation). Also, under normal circumstances we only have one
active timer at the `ProcessingTimeService` (`SystemProcessingTimeService`).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
