Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18487
@jinxing64 We have the default set the int max so that by default there is
no performance penalty for users. We have done some testing as Dhruve
mentioned but we don't regularly hit the issue. My plan was to set it to 20
just like mapreduce does as a starting point. The exact configuration can be
configuration dependent though as it depends on how much memory you give to
your NM's, how many requests in parallel you think you will have, etc. We do
plan on doing some more testing but it probably won't be for a couple days
---
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
