hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix some incorrect links in documentation

Browse Source
This commit is contained in:
Niclas Antti 2020-08-12 11:24:23 +03:00
parent 49ea5da9e2
commit 1bcc73666a
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/Filters/CCRFilter.md
View File

@ -44,7 +44,7 @@ The CCR filter has no mandatory parameters.
The time window during which queries are routed to the master. The duration
can be specified as documented
[here](Getting-Started/Configuration-Guide.md#durations)
[here](../Getting-Started/Configuration-Guide.md#durations)
but the value will always be rounded to the nearest second.
If no explicit unit has been specified, the value is interpreted as seconds
in MaxScale 2.4. In subsequent versions a value without a unit may be rejected.

4
Documentation/Filters/Cache.md
View File

@ -137,7 +137,7 @@ hard_ttl=60s
The default value is `0s`, which means no limit.
The duration can be specified as explained
[here](Getting-Started/Configuration-Guide.md#durations).
[here](../Getting-Started/Configuration-Guide.md#durations).
If no explicit unit has been specified, the value is interpreted as seconds
in MaxScale 2.4. In subsequent versions a value without a unit may be rejected.
@ -159,7 +159,7 @@ The default value is `0`, which means no limit. If the value of `soft_ttl` is
larger than `hard_ttl` it will be adjusted down to the same value.
The duration can be specifed as explained
[here](Getting-Started/Configuration-Guide.md#durations).
[here](../Getting-Started/Configuration-Guide.md#durations).
If no explicit unit has been specified, the value is interpreted as seconds
in MaxScale 2.4. In subsequent versions a value without a unit may be rejected.

6
Documentation/Filters/Throttle.md
View File

@ -77,7 +77,7 @@ This defines how long a session is allowed to be throttled before MaxScale
disconnects the session.
The value is specified as documented
[here](Getting-Started/Configuration-Guide.md#durations).
[here](../Getting-Started/Configuration-Guide.md#durations).
If no explicit unit is provided, the value is interpreted as milliseconds
in MaxScale 2.4. In subsequent versions a value without a unit may be rejected.
@ -96,7 +96,7 @@ Due to the underlying granularity of time measurment (as of June 2018), it is
not recommended that this value is set to less than 100 milliseconds.
The value is specified as documented
[here](Getting-Started/Configuration-Guide.md#durations).
[here](../Getting-Started/Configuration-Guide.md#durations).
If no explicit unit is provided, the value is interpreted as milliseconds
in MaxScale 2.4. In subsequent versions a value without a unit may be rejected.
@ -109,6 +109,6 @@ starts as soon as the filter throttles the frequency. Continuous throttling ends
when no throttling has been performed in the past `continuous_duration` time.
The value is specified as documented
[here](Getting-Started/Configuration-Guide.md#durations).
[here](../Getting-Started/Configuration-Guide.md#durations).
If no explicit unit is provided, the value is interpreted as milliseconds
in MaxScale 2.4. In subsequent versions a value without a unit may be rejected.