You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2022/04/21 18:59:32 UTC
[GitHub] [spark] otterc commented on pull request #36305: [WIP][SPARK-38987][shuffle] Handle fallback when merged shuffle blocks are corrupted and spark.shuffle.detectCorrupt is set to true
otterc commented on PR #36305:
URL: https://github.com/apache/spark/pull/36305#issuecomment-1105642564
I don't think we can handle corruption when it happens in between a shuffle chunk and fallback because we don't know how much of the chunk has been consumed. We would have to treat this as a corruption of a regular shuffle block and propagate it to driver. So, on the driver now we will have to handle fetch failures related to a shuffle chunk.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org