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.

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

refactor: add metrics for time travel and recent versions #18690

Merged
merged 4 commits into from
Sep 27, 2024

Conversation

zwang28
Copy link
Contributor

@zwang28 zwang28 commented Sep 25, 2024

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Add metrics to monitor the efficiency of compute node's recent versions and meta node's time travel.

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • I have added test labels as necessary. See details.
  • I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
  • My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
  • All checks passed in ./risedev check (or alias, ./risedev c)
  • My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)
  • My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

src/storage/src/monitor/hummock_state_store_metrics.rs Outdated Show resolved Hide resolved
@@ -740,6 +751,14 @@ impl MetaMetrics {
)
.unwrap();

let opts = histogram_opts!(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have we monitored the rate (frequency) of fetching time travel version?

Copy link
Contributor Author

@zwang28 zwang28 Sep 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it can be derived from time_travel_version_replay_latency.

Added to grafana.

@@ -342,7 +346,7 @@ impl HummockManager {
let sst_count = sst_ids.len();
let mut sst_id_to_info = HashMap::with_capacity(sst_count);
let sst_info_fetch_batch_size = std::env::var("RW_TIME_TRAVEL_SST_INFO_FETCH_BATCH_SIZE")
.unwrap_or_else(|_| "100".into())
.unwrap_or_else(|_| "10000".into())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we move this env var to the meta opt instead of implicitly reading an env var here?

And any reason to change from 100 to 10000?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we move this env var to the meta opt instead of implicitly reading an env var here?

OK

And any reason to change from 100 to 10000?

To speed up time travel version replay, i.e. less SELECT queries.

Copy link
Contributor

@wenym1 wenym1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zwang28 zwang28 added this pull request to the merge queue Sep 27, 2024
Merged via the queue into main with commit 8e6ebb0 Sep 27, 2024
32 of 33 checks passed
@zwang28 zwang28 deleted the wangzheng/add_metric branch September 27, 2024 12:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants