force TimerService to run the handler in alignment with the beginning of the second

[tbenr]

as discussed here: #6245 (comment)

as per my checks, time drift is always corrected back to be close to the tick of the second

Documentation

• I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

• I thought about adding a changelog entry, and added one if I deemed necessary.

[zilm13]

If I understand everything correctly, we have 999ms* seconds delay on start here in the worst case, but we run ticks every 500ms, so we could change it to have 499ms* in the worst case. Am I right?

[zilm13]

Also when system clock will be changed by some utility few ms forward or backwards, will we handle it?

[tbenr]

If I understand everything correctly, we have 999ms* seconds delay on start here in the worst case, but we run ticks every 500ms, so we could change it to have 499ms* in the worst case. Am I right?

yes that's correct

Also when system clock will be changed by some utility few ms forward or backwards, will we handle it?

very good question..........

[tbenr]

@zilm13 completely removed the startup delay :-)

[tbenr]

for the second question, I think quartz calculates next fire based on current time so it should react accordingly remaining aligned, but should be proven

[ajsutton]

Well that was unexpectedly simple. LGTM.