Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/18735#discussion_r129589282
--- Diff: docs/configuration.md ---
@@ -636,6 +636,8 @@ Apart from these, the following properties are also
available, and may be useful
<td>Long.MAX_VALUE</td>
<td>
The max number of chunks allowed to being transferred at the same time
on shuffle service.
+ Note that new coming connections will be closed when the max number is
hit. Client should
--- End diff --
change to say: allowed to be transferred
new coming should be new incoming.
Perhaps we could clarify a bit because Spark has a built in retry
mechanism. Could we rephrase to something like: The client will retry
according to the shuffle retry configs (see spark.shuffle.io.maxRetries and
spark.shuffle.io.retryWait), if those limits are reached the task will fail
with fetch failure.
---
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]
