Restart cluster does not have Prometheus topology
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
- What did you do?
Restart a cluster, which does not have Prometheus topology.
Just a reminder, there is a similar issue when cluster is upgraded: https://github.com/pingcap/tiup/issues/660
- What did you expect to see?
After restart, the Prometheus topology is assigned, behaves the same as "stop + start"
- What did you see instead?
Prometheus topology is still missing.
- What version of TiUP are you using (
tiup --version)?
v1.2.3 tiup
Go Version: go1.13
Git Branch: release-1.2
GitHash: df7e28a
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 reproducing a cluster restart and compare its behavior with the reported stop + start flow. Trace the restart path and the Prometheus topology assignment, using the linked upgrade issue for related context; done means Prometheus topology is present after restart and behaves as it does after stop + start.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- devops, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100