Dashboard cluster
Open
area/dashboard
- Dominant language
- Java
- Stars
- 23.1k
- Forks
- 8.1k
- PR merge metrics
- No merged PRs in 30d
Description
## Issue Description
Support for dashboard cluster
### Describe what happened (or what feature you want)
1.Manage more applications
2.Fail over
### How to reproduce it (as minimally and precisely as possible)
1. Persisting instances in heartbeat data to database.
2. Instances slicing：preempt instances through locks，and through the failure of the lock to do fail over.
3. Persisting metric data to database.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the dashboard heartbeat and metric persistence paths, then examine how instance locks are handled. Done means supporting multiple applications, persisting heartbeat and metric data, and failing over when lock acquisition fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100