-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
UCP: make memory usage of executors fit global memory limitation #15407
Labels
epic/memory-management
feature/accepted
This feature request is accepted by product managers
sig/execution
SIG execution
type/feature-request
Categorizes issue or PR as related to a new feature.
Comments
/pick-up-challenge |
@Yisaer pick up issue success |
This pick has been automatically canceled after more than a week. |
/pick-up-challenge |
@Yisaer pick up issue success |
This pick has been automatically canceled after more than a week. |
/pick-up-challenge |
@Yisaer pick up issue success |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
epic/memory-management
feature/accepted
This feature request is accepted by product managers
sig/execution
SIG execution
type/feature-request
Categorizes issue or PR as related to a new feature.
Description
Now nearly every executor has been tracking its memory usage using
memory.Tracker
. And here's amax-memory
configuration but is not taking effect on executors.If the memory usage of a SQL is exceeded by the global memory limitation, we need either,
Tips:
memory.Tracker
max-memory
is currently used by PrepareCache, we may need to find a way to re-implement it.Score
Mentor(s)
Contact the mentors: #tidb-challenge-program channel in TiDB Community Slack Workspace
Recommended Skills
Learning Materials
The text was updated successfully, but these errors were encountered: