Github user jinxing64 commented on the issue:
https://github.com/apache/spark/pull/18388
@cloud-fan
To be honest, it's a little bit tricky to reject "open blocks" by closing
the connection. The following reconnection will surely have extra cost. In
current change we are relying on retry mechanism of `RetryingBlockFetcher`.
`spark.shuffle.io.maxRetries` and `spark.shuffle.io.retryWait` should also be
tuned, with this change maybe their meanings become different, users should
know this. This is the sacrifice for compatibility.
It comes to me that can we add back `OpenBlocksFailed` and add a
flag(default false)? If user wants to turned on, we can tell them they should
upgrade the client.
---
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
