Skip to content

branch-3.0: [enhance](meta-service)collect fdb kv meta range info as metrics #52430 #53116

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

Jump to bottom
Merged
dataroaring merged 1 commit into from
Jul 12, 2025
Merged

branch-3.0: [enhance](meta-service)collect fdb kv meta range info as metrics #52430 #53116

dataroaring merged 1 commit into from
Jul 12, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jul 11, 2025

Cherry-picked from #52430

@koarz
[enhance](meta-service)collect fdb kv meta range info as metrics (#52430
60b3257 
)

API show_meta_ranges http response
```text
recycle|default_instance_id|txn: 1
meta|default_instance_id|tablet_index: 1
meta|default_instance_id|rowset_tmp: 1
```

metrics
```text
fdb_kv_ranges_count{category="recycle",instance_id="default_instance_id",sub_category="txn"} 1
fdb_kv_ranges_count{category="meta",instance_id="default_instance_id",sub_category="tablet_index"} 1
fdb_kv_ranges_count{category="meta",instance_id="default_instance_id",sub_category="rowset_tmp"} 1
```
@github-actions github-actions bot requested a review from dataroaring as a code owner July 11, 2025 08:46
@hello-stephen
Copy link
Contributor

hello-stephen commented Jul 11, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring reopened this Jul 11, 2025
@hello-stephen
Copy link
Contributor

hello-stephen commented Jul 11, 2025

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented Jul 11, 2025

Cloud UT Coverage Report

Increment line coverage 10.13% (8/79) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 83.26% (1149/1380)
Line Coverage 67.05% (19893/29669)
Region Coverage 66.78% (9857/14761)
Branch Coverage 55.93% (5152/9212)

dataroaring
dataroaring approved these changes Jul 12, 2025
View reviewed changes
Copy link
Contributor

@dataroaring dataroaring left a comment

Choose a reason for hiding this comment

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

LGTM

@dataroaring dataroaring merged commit 358c2aa into branch-3.0 Jul 12, 2025
24 of 25 checks passed
@github-actions github-actions bot deleted the auto-pick-52430-branch-3.0 branch July 12, 2025 02:18
@gavinchou gavinchou mentioned this pull request Aug 15, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dataroaring dataroaring dataroaring approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@hello-stephen @dataroaring @koarz