[
https://issues.apache.org/jira/browse/FLINK-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818929#comment-15818929
]
Andrey commented on FLINK-5449:
-------------------------------
Sorry, but I still don't understand how deploy/cleanup relates to the task
execution. Once task is executed, it immediately releases the lock and any
other resource (deploy or cleanup task) could acquire it.
I cannot find the code you are referring, could you paste it here?
Having metrics collected over different periods of time, makes them useless.
> Time drift in MetricRegistry
> ----------------------------
>
> Key: FLINK-5449
> URL: https://issues.apache.org/jira/browse/FLINK-5449
> Project: Flink
> Issue Type: Bug
> Components: Metrics
> Affects Versions: 1.2.0, 1.1.4, 1.3.0
> Reporter: Andrey
>
> Scheduled metrics are executed using "scheduleWithFixedDelay" which
> introduces time drift. See
> http://stackoverflow.com/questions/24649842/scheduleatfixedrate-vs-schedulewithfixeddelay
> for details.
> Expected:
>
> * switch to "scheduleatfixedrate"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
