-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
server: add store_id to hot ranges response api #76877
server: add store_id to hot ranges response api #76877
Conversation
6a4842b
to
669948c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 2 of 8 files at r1.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @dhartunian, @koorosh, @Santamaura, and @zachlite)
pkg/server/serverpb/status.proto, line 1232 at r5 (raw file):
// schema_name provides the name of schema (if exists) for table in current range. string schema_name = 9; int32 store_id = 10 [
nit: docstring
669948c
to
3511ea6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done! Thanks!
Reviewable status: complete! 0 of 0 LGTMs obtained (and 1 stale) (waiting on @dhartunian, @Santamaura, and @zachlite)
pkg/server/serverpb/status.proto, line 1232 at r5 (raw file):
Previously, dhartunian (David Hartunian) wrote…
nit: docstring
Done!
bors r+ |
Build failed: |
3511ea6
to
ff6cf57
Compare
This change extends HotRangesResponseV2 message to include store ID data. This information can be useful to investigate cause of hot ranges. Release note: None Release justification: bug fixes and low-risk updates to new functionality
ff6cf57
to
3a24e7e
Compare
bors r+ |
Build succeeded: |
This change extends HotRangesResponseV2 message
to include store ID data. This information can
be useful to investigate cause of hot ranges.
Release note: None
Release justification: bug fixes and low-risk updates to new functionality
Resolves: #76160