Skip to content
Snippets Groups Projects
Verified Commit fb7d5e6c authored by Vladimír Čunát's avatar Vladimír Čunát
Browse files

predict docs: be more explicit about recommended use

We're still run into people who thought that the example config
is a suitable default.  Example where it caused practical issues:
https://lists.nic.cz/hyperkitty/list/knot-resolver-users@lists.nic.cz/thread/WQDJJ3LLEIZ5U3VVSCITW6DZPICW4L7U/
parent 6693ab8b
Branches
Tags
1 merge request!1273Documentation nits
Pipeline #96427 passed with stages
in 41 minutes and 56 seconds
......@@ -22,7 +22,7 @@ Prediction
----------
The predict module can also learn usage patterns and repetitive queries,
though this mechanism is basically a prototype.
though this mechanism is a prototype and **not recommended** for use in production or with high traffic.
For example, if it makes a query every day at 18:00,
the resolver expects that it is needed by that time and prefetches it ahead of time.
......@@ -41,13 +41,12 @@ Example configuration
modules = {
predict = {
-- this mode is NOT RECOMMENDED for use in production
window = 15, -- 15 minutes sampling window
period = 6*(60/15) -- track last 6 hours
}
}
Defaults are as above: 15 minutes window, 6 hours period.
Exported metrics
----------------
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment