Skip to content

emit compaction pause duration metric in every compaction batch #19762

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

Merged
merged 1 commit into from
Apr 21, 2025

Conversation

miancheng7
Copy link
Contributor

Previously, the compaction pause duration metric was skipped if the number of keys was smaller than batchNum, leading to gaps in monitoring data. This change ensures the metric is emitted for every batch, regardless of key count.

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

@k8s-ci-robot
Copy link

Hi @miancheng7. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@fuweid
Copy link
Member

fuweid commented Apr 20, 2025

Hi @miancheng7 you need to sign it off by git commit -s --amend. thanks

Previously, the compaction pause duration metric was skipped if the number
of keys was smaller than `batchNum`, leading to gaps in monitoring data.
This change ensures the metric is emitted for every batch, regardless of
key count.

Signed-off-by: Miancheng Lin <[email protected]>
@miancheng7 miancheng7 force-pushed the fixCompactionPauseMetric branch from e66774b to 818dec3 Compare April 20, 2025 21:43
@miancheng7
Copy link
Contributor Author

Hi @miancheng7 you need to sign it off by git commit -s --amend. thanks
Thanks @fuweid , updated

@miancheng7
Copy link
Contributor Author

cc @ahrtr @chaochn47 for visibility, thanks!

@k8s-ci-robot
Copy link

@miancheng7: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@fuweid
Copy link
Member

fuweid commented Apr 20, 2025

/ok-to-test

Copy link

codecov bot commented Apr 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.76%. Comparing base (5122d43) to head (818dec3).
Report is 139 commits behind head on main.

Additional details and impacted files
Files with missing lines Coverage Δ
server/storage/mvcc/kvstore_compaction.go 100.00% <100.00%> (ø)

... and 30 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #19762      +/-   ##
==========================================
- Coverage   68.76%   68.76%   -0.01%     
==========================================
  Files         421      421              
  Lines       35897    35858      -39     
==========================================
- Hits        24686    24656      -30     
+ Misses       9783     9780       -3     
+ Partials     1428     1422       -6     

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5122d43...818dec3. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Member

@ahrtr ahrtr left a comment

Choose a reason for hiding this comment

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

LGTM

thx

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, fuweid, miancheng7

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ahrtr ahrtr merged commit 638b410 into etcd-io:main Apr 21, 2025
33 checks passed
@ahrtr
Copy link
Member

ahrtr commented Apr 21, 2025

/cherry-pick release-3.6

@ahrtr
Copy link
Member

ahrtr commented Apr 21, 2025

/cherry-pick release-3.5

@k8s-infra-cherrypick-robot

@ahrtr: new pull request created: #19770

In response to this:

/cherry-pick release-3.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-infra-cherrypick-robot

@ahrtr: new pull request created: #19771

In response to this:

/cherry-pick release-3.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ahrtr
Copy link
Member

ahrtr commented Apr 21, 2025

can you please update the changelog for 3.6 and 3.5? thx

@miancheng7
Copy link
Contributor Author

can you please update the changelog for 3.6 and 3.5? thx

sure, will do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

5 participants