[SPARK-26700][Core][FOLLOWUP] Add config spark.network.maxRemoteBlockSizeFetchToMem#27463
[SPARK-26700][Core][FOLLOWUP] Add config spark.network.maxRemoteBlockSizeFetchToMem#27463xuanyuanking wants to merge 2 commits intoapache:masterfrom
spark.network.maxRemoteBlockSizeFetchToMem#27463Conversation
77714a3 to
4201a93
Compare
There was a problem hiding this comment.
shall we move it to SparkConf.deprecatedConfigs?
There was a problem hiding this comment.
Thansk, done in 2d2637b.
|
Test build #117880 has finished for PR 27463 at commit
|
|
Test build #117886 has finished for PR 27463 at commit
|
|
Test build #117890 has finished for PR 27463 at commit
|
|
Test build #117888 has finished for PR 27463 at commit
|
Ngone51
left a comment
There was a problem hiding this comment.
Do we consider use configsWithAlternatives for this case? Which seems more convenient for such case.
2d2637b to
5c1f201
Compare
|
Make senes, done in 5c1f201 |
|
Test build #117932 has finished for PR 27463 at commit
|
|
Test build #117940 has finished for PR 27463 at commit
|
|
Retest this please. |
|
Test build #117946 has finished for PR 27463 at commit
|
|
|
||
| private[spark] val MAX_REMOTE_BLOCK_SIZE_FETCH_TO_MEM = | ||
| ConfigBuilder("spark.maxRemoteBlockSizeFetchToMem") | ||
| private[spark] val NETWORK_MAX_REMOTE_BLOCK_SIZE_FETCH_TO_MEM = |
There was a problem hiding this comment.
we can keep using MAX_REMOTE_BLOCK_SIZE_FETCH_TO_MEM
| AlternateConfig("spark.reducer.maxReqSizeShuffleToMem", "2.3")), | ||
| NETWORK_MAX_REMOTE_BLOCK_SIZE_FETCH_TO_MEM.key -> Seq( | ||
| AlternateConfig("spark.reducer.maxReqSizeShuffleToMem", "2.3"), | ||
| AlternateConfig("spark.maxRemoteBlockSizeFetchToMem", "3.0")), |
There was a problem hiding this comment.
will spark log warning message when these 2 alternatives are used? If not we still need to put them in deprecatedConfigs
There was a problem hiding this comment.
It will when user use old one, since deprecation warning also includes configsWithAlternatives:
spark/core/src/main/scala/org/apache/spark/SparkConf.scala
Lines 753 to 766 in 77510c6
There was a problem hiding this comment.
I tested locally, Spark will log warning messages.
|
Test build #117973 has finished for PR 27463 at commit
|
|
retest this please |
|
Test build #117981 has finished for PR 27463 at commit
|
|
retest this please |
|
Test build #117984 has finished for PR 27463 at commit
|
|
retest this please |
|
Test build #117986 has finished for PR 27463 at commit
|
|
thanks, merging to master/3.0! |
…kSizeFetchToMem` ### What changes were proposed in this pull request? Add new config `spark.network.maxRemoteBlockSizeFetchToMem` fallback to the old config `spark.maxRemoteBlockSizeFetchToMem`. ### Why are the changes needed? For naming consistency. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? Existing tests. Closes #27463 from xuanyuanking/SPARK-26700-follow. Authored-by: Yuanjian Li <xyliyuanjian@gmail.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com> (cherry picked from commit d861357) Signed-off-by: Wenchen Fan <wenchen@databricks.com>
…kSizeFetchToMem` ### What changes were proposed in this pull request? Add new config `spark.network.maxRemoteBlockSizeFetchToMem` fallback to the old config `spark.maxRemoteBlockSizeFetchToMem`. ### Why are the changes needed? For naming consistency. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? Existing tests. Closes apache#27463 from xuanyuanking/SPARK-26700-follow. Authored-by: Yuanjian Li <xyliyuanjian@gmail.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com>
What changes were proposed in this pull request?
Add new config
spark.network.maxRemoteBlockSizeFetchToMemfallback to the old configspark.maxRemoteBlockSizeFetchToMem.Why are the changes needed?
For naming consistency.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.