-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
76743: pkg/server: Add `TenantRanges` to status server, hook into debug.zip r=rimadeodhar a=abarganier While a system tenant or host cluster has full access to the debug information provided by the `Ranges` endpoint in the KV status server, tenants currently have no way to fetch metadata about their own ranges. We'd like to expose debug information in the form of range metadata to tenants, so that they can use this information in `debug.zip`, which is currently in the process of being exposed (albeit a subset of the full functionality) to tenants. To provide this, we implement `TenantRanges` and make it accessible within the tenant status server. The endpoint will reach across the Tenant/KV boundary via the tenant Connector interface to call the associated KV status server implementation. From here, we can lean on the existing `Ranges` endpoint. We can fan out requests to `Ranges` for all nodes containing replicas of ranges within the tenant's keyspace. The caller can then transform the metadata into a more tenant-appropriate format (e.g. avoiding concepts that break the 'tenant boundary', such as node IDs, replication information, etc). The results from all nodes are then combined, and returned back to the tenant caller. This PR does not contain pagination - this functionality will come in a follow up PR where we offset based on range startKeys. This PR also modifies the cluster-wide debug zip config to attempt a `TenantRanges` request, and generate a file from the response. This file will provide range metadata for all the leaseholder replicas available in the tenant's keyspace, which can be used by tenants for debug purposes, such as identifying hot ranges. Release note (api change): The status api will now have a newly exposed `_status/tenant_ranges` endpoint available to tenants, although it's not currently used except for debug.zip (see following commit). 77325: kvserver: downgrade & augment "slow raft ready" message r=erikgrinaker a=tbg It doesn't rise up to the level of a `Warning`, rather, it is informational. While I was here, I also added to the message that seeing it could indicate that the node (or storage) is overloaded. Triggered by an internal question[^1] about this message. [^1]: https://cockroachlabs.slack.com/archives/CHKQGKYEM/p1646245983917929 Release justification: low-risk logging improvement. Release note: None Co-authored-by: Alex Barganier <[email protected]> Co-authored-by: Tobias Grieger <[email protected]>
- Loading branch information
Showing
26 changed files
with
604 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.