github/node-problem-detector
1
0
Fork 0
mirror of https://github.com/kubernetes/node-problem-detector.git synced 2026-08-19 12:16:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document rule interval scheduling behavior

Browse Source 
State that rules with different intervals run on independent schedules.
State the concurrency limit and the catch-up behavior.
State the rule timeout validation limit.
This commit is contained in:
Veer Singh
2026-07-20 14:24:04 -07:00
parent 25105fd576
commit 798cc3bd1d
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/custom_plugin_monitor.md
+2 -2
View File
@@ -13,8 +13,8 @@
### Rule Config
* `timeout`: The JSON string sets the execution timeout for one rule.
* `invoke_interval`: The JSON string sets the invoke interval for one rule. The rule uses the global `invoke_interval` when this field is absent.
* `timeout`: The execution timeout for one rule. A rule `timeout` greater than the global `timeout` fails validation at startup.
* `invoke_interval`: The invoke interval for one rule. The rule uses the global `invoke_interval` when this field is absent. Rules with different effective intervals run on independent schedules. Their plugins can run at the same time, up to the global `concurrency` limit. A rule never runs concurrently with itself. The monitor runs at most one catch-up batch when a batch overruns its interval.
For example, this rule runs every seven seconds: