Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Description of resource-monitor-warning-interval is confusing #10107

Open
matthewdarwin opened this issue Mar 3, 2021 · 2 comments
Open

Description of resource-monitor-warning-interval is confusing #10107

matthewdarwin opened this issue Mar 3, 2021 · 2 comments
Labels
documentation Requires attention from documentation team. e.g. documentation is expected to be generated. track-in-jira

Comments

@matthewdarwin
Copy link

In nodeos --print-default-config it says

# Number of resource monitor intervals between two consecutive warnings when the threshold is hit. Should be between 1 and 450 (eosio::resource_monitor_plugin)
# resource-monitor-warning-interval = 30

Does this mean that the disk space must have exceeded the limit at least this many seconds apart? The default is to check every 2 seconds, so this means if the problem is occurring for 32 seconds (30 seconds + 2 seconds), then nodeos will shutdown?

I think the description could be clarified, if this is the case.

Also, the entire documentation is missing for eosio::resource_monitor_plugin, (issue is #9839), so I can't look there either.

@matthewdarwin
Copy link
Author

2.1.0-rc3

@aclark-b1 aclark-b1 added documentation Requires attention from documentation team. e.g. documentation is expected to be generated. track-in-jira labels Mar 3, 2021
@linhuang-blockone
Copy link
Contributor

resource-monitor-interval-seconds and resource-monitor-warning-interval are independent. The resource monitor plugin checks space every resource-monitor-interval-seconds. If resource-monitor-not-shutdown-on-threshold-exceeded is set, it prints out warning every resource-monitor-warning-interval when used space exceeds threshold.

Documentation will be added.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Requires attention from documentation team. e.g. documentation is expected to be generated. track-in-jira
Projects
None yet
Development

No branches or pull requests

3 participants