node_id or store_id in SHOW EXPERIMENTAL_RANGES

[neeral]

Exalate commented:

The documentation for SHOW EXPERIMENTAL_RANGES says that the output contains node IDs.

Which nodes contain the range replicas

https://www.cockroachlabs.com/docs/v2.1/show-experimental-ranges.html

However, I've observed that the "replicas" column actually outputs store IDs, not node IDs. I've observed this on both cockroach v2.0 and v2.1. It is probably also present on newer versions, haven't checked though.

Is this a bug in the documentation or in the SQL command?

To Reproduce
Create a cluster which has some nodes whose store IDs do not match their node IDs. Create some tables. Run show experimental ranges. Compare the "replicas" column in output with that of the range report (from admin UI).

Jira Issue: DOC-405

[RoachietheSupportRoach]

Zendesk ticket #4347 has been linked to this issue.

[roncrdb]

Hey @neeral ,

I've tried to reproduce this on my end with both 19.2 and 2.1 but was not able to.

Could you share a screenshot of what the UI reads when you go to a range report under HOST/#/reports/range/<RANGE_ID>.

You should see something that looks like this n3 s3 r4/2 at the bottom of the first section in the range report.

Thanks!

[neeral]

Output of SHOW EXPERIMENTAL_RANGES shows replicas are 54, 55 and 56.

$ cockroach sql -e "show experimental_ranges from table foo"
   start_key   |   end_key    | range_id |  replicas  | lease_holder  
+--------------------------------------------+--------------------------------------------+----------+------------+--------------+
  NULL         | <end-key>    |      982 | {54,55,56} |           56  

I'm unable to get a screenshot of the admin UI right now. However, here is output of debug endpoint _status/range/982. This should be the same as what would be shown on the UI. It shows that 54, 55 and 56 are store IDs, not node IDs.
r982.txt

Cockroach version is v2.1.9.

[petermattis]

@neeral This looks like a docs issue.

On master, SHOW {RANGES,EXPERIMENTAL_RANGES} is populated from crdb_internal.ranges. That virtual table contains store IDs in the replicas column. Looks like v2.1.9 has similar code:

	var replicas []int
	for _, rd := range desc.Replicas {
		replicas = append(replicas, int(rd.StoreID))
	}

The docs also claim that the lease_holder column is the node, but it too is the replica's store ID.

Assigning to @jseldess as a docs issue.

[neeral]

Thanks @petermattis for clarifying.

[jseldess]

Thanks, @neeral and @petermattis. I'll transfer this issue to our docs repo.