pingcap / pingcap/tidb-operator
should remove ng-monitoring /info key in PD(etcd) after ng-monitoring has been deleted.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Bug Report
this issue is similar to https://github.com/pingcap/tiup/issues/1752.
ng-monitoring also write 2 keys into PD(etcd), after ng-monitoring has been deleted, we should delete the info key in PD(etcd), just like delete TiDB info key in PD(etcd).
What did you see instead?
Contributor guide
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
Start by reading the existing TiDB info-key deletion path and compare it with the ng-monitoring deletion flow described here and in issue #1752. Confirm which ng-monitoring info key remains in PD(etcd), then verify that deleting ng-monitoring also removes it without affecting other keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100