This repository was archived by the owner on Apr 2, 2024. It is now read-only.
Aggregates for downsampling caggs#602
Draft
jgpruitt wants to merge 17 commits intofeature_metric_rollupfrom
Draft
Aggregates for downsampling caggs#602jgpruitt wants to merge 17 commits intofeature_metric_rollupfrom
jgpruitt wants to merge 17 commits intofeature_metric_rollupfrom
Conversation
Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com>
This commit does 3 things on a high level.
1. create_metric_rollup is a straightforward that creates schema based on rollup name, prefixed with 'ps_'.
2. Functions to create metric rollup depending on metric type. This is done by
a function scan_for_new_rollups that runs every 30 mins. This function looks for
pending metrics (by peeking inside metric_with_rollup table) that need rollups
and creates them. The creation path is
scan_for_new_rollups -> create_metric_rollup_view (decides the metric type) -> create_rollup_for_{gauge|counter|summary}.
Counter and Histogram have similar columns, hence handled by the same function.
3. Adds set of utility functions like counter_reset_sum and irate, which are required for rollup creation. These
are temporary functions and they MUST be removed before the MVP.
Note: These functions are just dummies, their behaviour is not 100% correct.
Example: These functions require ordered values array, but we cannot do ORDER BY in Caggs query.
Hence, these functions will be handled by SQL aggregate written in Rust.
Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com>
Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com>
Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com>
Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com> This commit does 2 things: 1. Update the prom_api.register_metric_view() to accept refresh_interval information 2. Creates a Cagg refresher job that is per resolution. This job is created by `create_cagg_refresh_job` after confirming no job related to the given resolution exists for refresh Note: 1. We need to register the newly created metric-rollups using register_metric_view(). This is done in the `scan_for_new_rollups` after storing the new Caggs metadata in a temp table. This is to register the Caggs only after all views are created, otherwise we get a Error while creating materialized view, saying the Caggs already exists. 2. In register_metric_view() table, we skip the checks offered by `get_first_level_view_on_metric()` since based on a quick investigation, these checks do not work when the Caggs are created with `timescaledb.materialized=true`. Moreover, since we are creating Caggs internally in metric-rollups, we need not worry about Cagg view created (which is done by those checks).
Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com> This commit does 2 things: handle compression and retention for metric-rollups and custom Caggs for downsampling. The comments on `How?` are present as comments on the respective functions.
…ple. Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com>
…ompressing Caggs. Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com> This PR does 2 things: 1. Fixes the exception Caggs already exists that was caused when a cagg for one resolution was again created when the `scan_for_new_rollups()` was re-executed. Added a test under `metric_rollups_scan_for_new_rollups` to ensure correct behaviour. 2. `execute_caggs_compression_policy()` used to panic when looping over already compressed chunk of a Cagg that has some uncompressed chunks that need compression. Added rerunning compression policy to ensure correct behaviour.
Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com>
Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com>
Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com>
sumerman
reviewed
Jan 9, 2023
| } | ||
| } | ||
|
|
||
| #[allow(clippy::too_many_arguments)] |
Contributor
There was a problem hiding this comment.
Since 0.3.x pgx has a native support for aggregates https://github.com/tcdi/pgx/blob/master/pgx-examples/aggregate/src/lib.rs and we ourselves had wanted to move to use it #62
This is not a deal breaker, but it would be my preference if we didn't go the legacy path for newly introduced aggregates.
Collaborator
Author
There was a problem hiding this comment.
Ahh. Cool. I didn't realize that.
| #[derive(Serialize, Deserialize, PostgresType, Debug)] | ||
| #[pgx(sql = false)] | ||
| pub struct CounterResetState { | ||
| prior: (i64, f64), |
Contributor
There was a problem hiding this comment.
My preference would be a structure with named fields
harkishen
force-pushed
the
feature_metric_rollup
branch
2 times, most recently
from
6c3abd9 to
ca87ecd
Compare
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Description
Merge requirements
Please take into account the following non-code changes that you may need to make with your PR: