[native] Deprecate kQueryMaxTotalMemoryPerNode config#18842
Merged
amitkdutta merged 1 commit intoprestodb:masterfrom Dec 25, 2022
Merged
[native] Deprecate kQueryMaxTotalMemoryPerNode config#18842amitkdutta merged 1 commit intoprestodb:masterfrom
amitkdutta merged 1 commit intoprestodb:masterfrom
Conversation
…iate user and system memory
xiaoxmeng
requested review from
amitkdutta,
mbasmanova,
spershin and
tanjialiang
Contributor
|
Thank for the fix @xiaoxmeng |
amitkdutta
approved these changes
Dec 25, 2022
amitkdutta
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deprecate kQueryMaxTotalMemoryPerNode as Velox doesn't
differentiate user and system memory. Also improve the test
check logic to ease error debug