[SPARK-47000][CORE] Use getTotalMemorySize
in WorkerArguments
#45060
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.
What changes were proposed in this pull request?
This PR aims to use
getTotalMemorySize
instead of deprecatedgetTotalPhysicalMemorySize
(OpenJDK) orgetTotalPhysicalMemory
(IBM Java) inWorkerArguments
.Why are the changes needed?
getTotalPhysicalMemorySize
is deprecated at Java 14 in OpenJDK.getTotalPhysicalMemory
is deprecated since 1.8 in IBM.getTotalMemorySize
is recommended in both environments for Apache Spark 4.0.0 because the minimum Java version is 17.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs with the existing test cases.
Was this patch authored or co-authored using generative AI tooling?
No.