fix(runloop) reschedule rebuild timers after running them #8567
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Router and plugin iterator rebuild timers were scheduled using
ngx.timer.every
. If the rebuild processes took longer thanworker_state_update_frequency
to execute, they would start again while the previous one was still running.Full changelog
ngx.timer.every
calls tongx.timer.at
."plugins iterator was changed while rebuilding it"
is now logged as an info message.Issue reference
There were multiple reports of
"plugins iterator was changed while rebuilding it"
logged as error.Fix #8525
FTI-3239