squito commented on issue #23453: [SPARK-26089][CORE] Handle corruption in large shuffle blocks URL: https://github.com/apache/spark/pull/23453#issuecomment-459527473 sorry my earlier comment wasn't clear -- ankur was confused too but I think this version of the patch implements what I think the right option is: * by default, do not copy into memory at all, but do on-the-fly detection of corruption. This alway results in a fetch-failure * optionally, go back to the old behavior, to copy into memory if the block is small. Then you'd first retry pulling the data, and throw a fetch failure after that. Turned on with "spark.shuffle.detectCorrupt.useExtraMemory=true" * optionally, never do any check, even on the fly (using the old config, "spark.shuffle.detectCorrupt=false")
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
