Skip to content
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

Cluster with multiple stores per-node indicates "undefined" in the Databases tab #118473

Open
world2mark opened this issue Jan 30, 2024 · 1 comment
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.

Comments

@world2mark
Copy link

world2mark commented Jan 30, 2024

Create a cluster (say 3 nodes), with multiple stores for example:

              exec /cockroach/cockroach
              start
              --cache=.25
              --logtostderr
              --certs-dir=/cockroach/cockroach-certs
              --locality=region=CA-East,zone=Zone-1
              --store=path=crdb_store-0,ballast-size=0
              --store=path=crdb_store-1,ballast-size=0
              --store=path=crdb_store-2,ballast-size=0
              --sql-addr=:26257
              --listen-addr=:26357
              --advertise-addr=172.23.0.4:31850
              --locality-advertise-addr=zone=Zone-1@zlamal-172-23-0-4-mesh-local.crdb-canada:26357
              --join 172.23.0.4:31850,172.23.0.5:31851,172.23.0.6:31852

This example is 1 of 3 nodes, * 3 stores, totalling 9 stores for the cluster (hence the n1...n9 in the following screenshot).

When you look at the Console UI:

  1. it looks like there are 9 nodes, but it's actually 9 stores (3 nodes).
  2. CA-East is the only region defined, so the stores (n1, n2, n3) appear to be synced-up with the nodes 1, 2,3.
  3. "undefined" shows up for the rest of the stores (n4...n9).
  • UI should be more clear on what are "nodes" and what are "stores"
  • UI should address the "undefined" regionality

image

CRDB ver 23.1.11

Jira issue: CRDB-35753

@world2mark world2mark added the C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. label Jan 30, 2024
@xinhaoz
Copy link
Member

xinhaoz commented Feb 12, 2024

This is probably due to #118957.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Projects
None yet
Development

No branches or pull requests

2 participants