Add the PD leader check for PD_miss_peer_region_count
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 29
- Forks
- 46
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 17
Description
PD_miss_peer_region_count kept triggering because it was not checking if the alert is issued by the current pd leader or not.
I see that we currently adjust pd_cluster_low_space, pd_cluster_lost_connect_tikv_nums and pd_pending_peer_region_count but not PD_miss_peer_region_count.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the alert definitions for PD_miss_peer_region_count and compare them with pd_cluster_low_space, pd_cluster_lost_connect_tikv_nums, and pd_pending_peer_region_count. Check how those alerts determine whether the current PD leader issued them. Done means PD_miss_peer_region_count applies the same leader check and no longer triggers from non-leader PD instances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100