You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2021/01/07 08:34:06 UTC

[GitHub] [druid] leventov commented on pull request #10448: Added CronScheduler support as a proof to clock drift while emitting metrics

leventov commented on pull request #10448:
URL: https://github.com/apache/druid/pull/10448#issuecomment-755968409


   > Hi @leventov, as test coverage is not very great for Druid metrics system, I'm wondering how much the CronScheduler is well-tested in production environment, especially when it runs for a long time period. Could you give me some idea?
   
   I don't know of any production deployment of CronScheduler. However, I want to note that the fact that metric/monitoring systems are not well-tested is precisely _the_ reason to introduce CronScheduler, which is engineered for the sole purpose to be more stable than standard library executors.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org