80 lines
1.9 KiB
Markdown
80 lines
1.9 KiB
Markdown
|
[Documentation](../../README.md#documentation) → [Configuration](../config.en.md) → Monitor Parameters
|
||
|
|
|
||
|
|
-----
|
||
|
|
|
||
|
|
[Читать на русском](monitor.ru.md)
|
||
|
|
|
||
|
|
# Monitor Parameters
|
||
|
|
|
||
|
|
These parameters only apply to Monitors.
|
||
|
|
|
||
|
|
- [etcd_mon_ttl](#etcd_mon_ttl)
|
||
|
|
- [etcd_mon_timeout](#etcd_mon_timeout)
|
||
|
|
- [etcd_mon_retries](#etcd_mon_retries)
|
||
|
|
- [mon_change_timeout](#mon_change_timeout)
|
||
|
|
- [mon_stats_timeout](#mon_stats_timeout)
|
||
|
|
- [osd_out_time](#osd_out_time)
|
||
|
|
- [placement_levels](#placement_levels)
|
||
|
|
|
||
|
|
## etcd_mon_ttl
|
||
|
|
|
||
|
|
- Type: seconds
|
||
|
|
- Default: 30
|
||
|
|
- Minimum: 10
|
||
|
|
|
||
|
|
Monitor etcd lease refresh interval in seconds
|
||
|
|
|
||
|
|
## etcd_mon_timeout
|
||
|
|
|
||
|
|
- Type: milliseconds
|
||
|
|
- Default: 1000
|
||
|
|
|
||
|
|
etcd request timeout used by monitor
|
||
|
|
|
||
|
|
## etcd_mon_retries
|
||
|
|
|
||
|
|
- Type: integer
|
||
|
|
- Default: 5
|
||
|
|
|
||
|
|
Maximum number of attempts for one monitor etcd request
|
||
|
|
|
||
|
|
## mon_change_timeout
|
||
|
|
|
||
|
|
- Type: milliseconds
|
||
|
|
- Default: 1000
|
||
|
|
- Minimum: 100
|
||
|
|
|
||
|
|
Optimistic retry interval for monitor etcd modification requests
|
||
|
|
|
||
|
|
## mon_stats_timeout
|
||
|
|
|
||
|
|
- Type: milliseconds
|
||
|
|
- Default: 1000
|
||
|
|
- Minimum: 100
|
||
|
|
|
||
|
|
Interval for monitor to wait before updating aggregated statistics in
|
||
|
|
etcd after receiving OSD statistics updates
|
||
|
|
|
||
|
|
## osd_out_time
|
||
|
|
|
||
|
|
- Type: seconds
|
||
|
|
- Default: 600
|
||
|
|
|
||
|
|
Time after which a failed OSD is removed from the data distribution.
|
||
|
|
I.e. time which the monitor waits before attempting to restore data
|
||
|
|
redundancy using other OSDs.
|
||
|
|
|
||
|
|
## placement_levels
|
||
|
|
|
||
|
|
- Type: json
|
||
|
|
- Default: `{"host":100,"osd":101}`
|
||
|
|
|
||
|
|
Levels for the placement tree. You can define arbitrary tree levels by
|
||
|
|
defining them in this parameter. The configuration parameter value should
|
||
|
|
contain a JSON object with level names as keys and integer priorities as
|
||
|
|
values. Smaller priority means higher level in tree. For example,
|
||
|
|
"datacenter" should have smaller priority than "osd". "host" and "osd"
|
||
|
|
levels are always predefined and can't be removed. If one of them is not
|
||
|
|
present in the configuration, then it is defined with the default priority
|
||
|
|
(100 for "host", 101 for "osd").
|