[VL] Recover broken memory-trace option spark.gluten.backtrace.allocation #6635
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.
spark.gluten.backtrace.allocation
was added in #3069 to print backtrace of large memory allocations into log.The option was broken for a while and the PR is to recover the logic of it.
Additionally, option key
spark.gluten.backtrace.allocation
will be changed tospark.gluten.memory.backtrace.allocation
.