Skip to content

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

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
morrySnow merged 1 commit into from
Jul 14, 2025
Merged

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

morrySnow merged 1 commit into from
Jul 14, 2025

Conversation

@koarz
Copy link
Contributor

@koarz koarz commented Jul 14, 2025 •
edited by morrySnow
Loading

picked from #52430

@koarz
[enhance](meta-service)collect fdb kv meta range info as metrics (apa…
d9290bd 
…che#52430)

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
```
@koarz koarz requested a review from morrySnow as a code owner July 14, 2025 03:13
@hello-stephen
Copy link
Contributor

hello-stephen commented Jul 14, 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?

@koarz
Copy link
Contributor Author

koarz commented Jul 14, 2025

run buildall

@doris-robot
Copy link

doris-robot commented Jul 14, 2025

Cloud UT Coverage Report

Increment line coverage 10.13% (8/79) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 81.13% (1187/1463)
Line Coverage 65.31% (20569/31494)
Region Coverage 66.78% (10431/15620)
Branch Coverage 56.55% (5508/9740)

@morrySnow morrySnow changed the title branch-3.1: [enhance](meta-service)collect fdb kv meta range info as metrics(#52430) branch-3.1: [enhance](meta-service)collect fdb kv meta range info as metrics #52430 Jul 14, 2025
@morrySnow morrySnow merged commit a90c803 into apache:branch-3.1 Jul 14, 2025
23 checks passed
@koarz koarz deleted the meta_ranges_3.1 branch July 14, 2025 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@morrySnow morrySnow morrySnow 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

@koarz @hello-stephen @doris-robot @morrySnow