Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note on partial downloads. #1226

Merged
merged 3 commits into from
Oct 29, 2024
Merged

Add note on partial downloads. #1226

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f07c6f1
Add note on partial downloads.
david-fritz-gravwell Oct 29, 2024
1923331
Update admin/limits.md
david-fritz-gravwell Oct 29, 2024
8fa27c6
Update admin/limits.md
david-fritz-gravwell Oct 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions admin/limits.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,10 @@ If you're seeing messages about render storage limits when running your searches

To prevent users from filling up the disk with over-large queries, use the `Render-Store-Limit` parameter in the webserver's gravwell.conf file. Setting `Render-Store-Limit=64`, for instance, would set a limit of 64 MB of on-disk storage per query. The default is 1024MB; this gives users a great deal of space to work with while hopefully preventing free space issues on modern disks.

### Partial Results In Renderer Storage Limited Scenarios

Attempting to download, share, or save results for a search that has reached the render storage limit will display a warning about partial results. If you're seeing this message, it's important to understand that the data entries for this action will only be valid up to the point where the render storage limit was reached, regardless of what the overview chart indicates.

## Gravwell Resource Size

User-created [resources](/resources/resources) can take up a lot of space on disk, on both the webserver and the indexers. In addition, one of the most common uses of resources is to provide lookup tables; in order to use a resource as a lookup table, the *entire* resource must be loaded into memory, meaning that running many simultaneous queries with extremely large lookup tables can put the system at risk of an out-of-memory state. The `Resource-Max-Size` parameter in gravwell.conf specifies a limit, in bytes, for resource size. Thus, setting `Resource-Max-Size=20971520` will limit resources to no more than 20 megabytes.
Expand Down