tikv/tikv

Scheduler: use local metrics

Open

#2648 opened on Jan 5, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (15,922 stars) (2,189 forks)batch import
component/storagedifficulty/mediumhelp wantedtype/enhancement

Description

We have already refactored worker, so now we can use worker + timer for the scheduler. We can use the local metrics and then flush to global metrics in a timer.

Contributor guide

Tech stack
rust
Domain
backenddatabaseobservability
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingunderstanding of TiKV schedulerknowledge of metrics frameworks
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
This issue proposes using local metrics in the scheduler and flushing to global metrics via a timer. First, review the current refactoring of the worker module to understand the pattern. Look for files related to scheduler metrics in the source code, likely under `src/scheduler/` or `components/metrics/`. Check if the architecture has changed significantly since 2018, as the issue is old. No linked PRs or comments exist, so you may need to confirm with maintainers if this is still relevant and if there are any pending dependencies.