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 2019/10/31 09:59:46 UTC

[GitHub] [spark] cloud-fan commented on issue #26206: [SPARK-29551][CORE] Fix a bug about fetch failed when an executor is lost

cloud-fan commented on issue #26206: [SPARK-29551][CORE] Fix a bug about fetch failed when an executor is lost
URL: https://github.com/apache/spark/pull/26206#issuecomment-548294304
 
 
   @weixiuli can you describe the problem and your fix at high-level? i.e. do not mention the detailed code.
   
   > As we all know that the previous will callmapOutputTracker.removeOutputsOnHost(host)or
   mapOutputTracker.removeOutputsOnExecutor(execId) when reduce stage fetches failed and the executor is active, while it does NOT for the above problems.
   
   This is pretty hard to understand, please use phrases like "clear shuffle status for a host", "clear shuffle status for a mapper", etc.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org