Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18388
+1 on both.
We have to do it at server side, because there may be a lot of reducers
fetching data from one shuffle service at the same time, which may OOM the
server even each reducer has a limited requests size to this server.
And we also need to do it at reducer side, in case several reducers exhaust
the shuffle service and make all reducers waiting.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
