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

server: add store_id to hot ranges response api #76877

Merged

Conversation

koorosh
Copy link
Collaborator

@koorosh koorosh commented Feb 22, 2022

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

@koorosh koorosh requested a review from a team as a code owner February 22, 2022 08:04
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@koorosh koorosh force-pushed the add-stores-field-to-hot-ranges-response branch from 6a4842b to 669948c Compare February 22, 2022 09:21
Copy link
Collaborator

@dhartunian dhartunian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm: just add docstring :)

Reviewed 2 of 8 files at r1.
Reviewable status: :shipit: 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

@koorosh koorosh force-pushed the add-stores-field-to-hot-ranges-response branch from 669948c to 3511ea6 Compare March 2, 2022 23:18
Copy link
Collaborator Author

@koorosh koorosh left a 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: :shipit: 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!

@koorosh
Copy link
Collaborator Author

koorosh commented Mar 3, 2022

bors r+

@craig
Copy link
Contributor

craig bot commented Mar 3, 2022

Build failed:

@koorosh koorosh force-pushed the add-stores-field-to-hot-ranges-response branch from 3511ea6 to ff6cf57 Compare March 3, 2022 10:18
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
@koorosh koorosh force-pushed the add-stores-field-to-hot-ranges-response branch from ff6cf57 to 3a24e7e Compare March 3, 2022 11:58
@koorosh
Copy link
Collaborator Author

koorosh commented Mar 3, 2022

bors r+

@craig
Copy link
Contributor

craig bot commented Mar 3, 2022

Build succeeded:

@craig craig bot merged commit d075b79 into cockroachdb:master Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

See stores in hot ranges page v1
3 participants