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.api add api for history_hot_region info;server.cluster add storage for hot region;sever.config add 'hot-regions-reserved-days' and 'hot-region-write-interval' #3988

Closed
wants to merge 11 commits into from

Conversation

qidi1
Copy link
Contributor

@qidi1 qidi1 commented Aug 15, 2021

What problem does this PR solve?
Store hot-region information regularly
Provide api interface for requesting historical hot-region information
What is changed and how it works?
By introducing part of the heartbeat processing logic in the client of region_syncer, unnecessary saveKV operations are reduced.

  • Notable feature additions
    Add history hot region info store and request for it
  • API changes
    Add a post method,api is /hotspot/regions/history
    Check List

Tests

Unit test

Code changes

Side effects

Related changes

Release note

@ti-chi-bot
Copy link
Member

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot
Copy link
Member

@qidi1: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ti-chi-bot ti-chi-bot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Aug 15, 2021
@ti-chi-bot ti-chi-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 15, 2021
@qidi1
Copy link
Contributor Author

qidi1 commented Aug 15, 2021

some code is confict,so i close this push request and push a new push request

@qidi1 qidi1 closed this Aug 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants