Github user dhruve commented on a diff in the pull request:
https://github.com/apache/spark/pull/18487#discussion_r125945263
--- Diff:
core/src/main/scala/org/apache/spark/internal/config/package.scala ---
@@ -321,6 +321,16 @@ package object config {
.intConf
.createWithDefault(3)
+ private[spark] val REDUCER_MAX_BLOCKS_IN_FLIGHT_PER_ADDRESS =
+ ConfigBuilder("spark.reducer.maxBlocksInFlightPerAddress")
--- End diff --
@jinxing64 After your fix for lazily loading the open blocks iterator, I am
not seeing issues with the NM crashing on my end. However, in cases where a
request was being made with a high no. of blocks which were under the max
constraints caused increased load. This is an added layer of defense which can
mitigate the issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
