-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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.
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
Support time based retention #17413
Merged
Merged
Support time based retention #17413
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stelfrag
force-pushed
the
limit_tier0_update_every
branch
3 times, most recently
from
April 23, 2024 11:36
db8ff30
to
56f2033
Compare
stelfrag
force-pushed
the
limit_tier0_update_every
branch
2 times, most recently
from
April 29, 2024 06:35
d280a21
to
fbec2cb
Compare
ilyam8
force-pushed
the
limit_tier0_update_every
branch
from
May 6, 2024 10:26
fb168d5
to
b3f487e
Compare
stelfrag
force-pushed
the
limit_tier0_update_every
branch
2 times, most recently
from
May 13, 2024 10:57
15c5f52
to
6dc60fa
Compare
thiagoftsm
reviewed
May 14, 2024
@stelfrag I ran different tests with this PR, and I did not observe anything anomalous:
Tests were done compiling with |
stelfrag
force-pushed
the
limit_tier0_update_every
branch
from
May 16, 2024 07:51
1b3f212
to
b3d37a9
Compare
@stelfrag please rebase this to test it. |
stelfrag
force-pushed
the
limit_tier0_update_every
branch
3 times, most recently
from
May 24, 2024 10:10
05df1cf
to
8c27b66
Compare
stelfrag
force-pushed
the
limit_tier0_update_every
branch
from
May 28, 2024 09:34
8c27b66
to
0259ebe
Compare
ilyam8
reviewed
Jun 3, 2024
stelfrag
force-pushed
the
limit_tier0_update_every
branch
from
June 3, 2024 13:00
bdabe32
to
6416443
Compare
ilyam8
reviewed
Jun 3, 2024
stelfrag
force-pushed
the
limit_tier0_update_every
branch
6 times, most recently
from
June 5, 2024 19:55
d84d12b
to
3fe699b
Compare
thiagoftsm
reviewed
Jun 6, 2024
Add new dbengine tier 0 multihost disk space MB Time based retention defaults to disabled if all parameters are default
Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
…ngine tier 0 multihost disk space MB" is not specified
Calculated disk space matches the calculated used for datafile rotation Fix percentage contribution calculation of metadata to each tier
…ion charts vs space reported in /api/v2/node_instances
RRDENG_MIN_DISK_SPACE_MB 256 MB (from 64) dbengine multihost disk space MB maps to dbengine tier 0 disk space MB Disk space for tiers "dbengine tier X disk space MB"
…netdata.conf output
… migration of options Rename options
… MB. If the value is non zero for tier 0, it must be at least 256 MB
stelfrag
force-pushed
the
limit_tier0_update_every
branch
from
June 6, 2024 08:49
7d38f7d
to
7164004
Compare
ilyam8
approved these changes
Jun 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes: #17082
Changes
dbengine tier x disk space MB = nnnn
dbengine tier 0 disk space MB = 1024
dbengine tier x retention days = nnnn
dbengine tier 0 retention days = 14
dbengine tier backfill
dbengine tier x disk space MB
options can be 0 to use as much space needed for the desired time based retentionThe disk space related options
have been removed. The
dbengine multihost disk space MB
is automatically renamed todbengine tier 0 disk space MB
Similarly to configure db space for other tiers (up to 5) eg
You can disable disk space checks (use available space) by specifying 0 as disk space eg.
Defaults
The default settings on a newly installed agent when no options are set are:
Time retention not automatically activated
If the following options have been specified in the config (
[db]
section) the retention days will not beautomatically activated. In this case the
dbengine tier x retention days
option must be used.