LeeeeLiu opened a new pull request, #37819:
URL: https://github.com/apache/spark/pull/37819
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'core/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
Add two parameters to allow customizing maxBroadcastTableBytes and
maxBroadcastRows
### Why are the changes needed?
Recently, we encountered some driver OOM problems. Some tables with large
data volume were compressed using Snappy and then broadcast join was performed,
but the actual data volume was too large, which resulted in driver OOM.
The values of maxBroadcastTableBytes and maxBroadcastRows are hardcoded, 8GB
and 512000000 respectively. Maybe we can allow customization of these values,
configure smaller values according to different scenarios, and prohibit
broadcast joins for tables with large data volumes to avoid driver OOM.
### Does this PR introduce _any_ user-facing change?
NO
### How was this patch tested?
Unit test
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
