-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ui: make per-node views actually per-node #18452
Comments
This actually has a use, though. Each node has its own view of how many live nodes there are in the cluster at a time. If a node is far behind or partitioned away from the others, its reported node count will be different from the count reported by the other nodes. We'd probably be better off calling the graph "Live Node Count" rather than just "Node Count", but I don't think we want to change what it shows. |
Ok, that makes sense, although it begs the question of if having this as a time series graph is really the right approach. It makes me think that we should have a view that shows what each node currently sees as cluster state. We are unlikely to have time to do this in 1.2, so I think your approach of calling it that, and perhaps adding a tooltip of why it matters would be an appropriate first step. |
Addresses cockroachdb#18452 for 1.1
Addresses cockroachdb#18452 for 1.1
Addresses cockroachdb#18452 for 1.1
This naturally rolls into some bigger IA questions. Notably, some charts show aggregates for the cluster as a whole and other show a breakdown by node. Some charts (such as latency) have several different percentile charts, where having a single chart showing multiple percentiles would be more valuable. |
haha, don't open the can of worms @couchand! jk, but yes agree that we should approach this problem holistically when we get to it. |
We have marked this issue as stale because it has been inactive for |
On the per node view in the admin UI, we are showing node list. This is confusing from an information architecture perspective, since that is a cluster-wide metric.
The text was updated successfully, but these errors were encountered: