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 2021/09/16 23:31:56 UTC

[GitHub] [spark] mridulm edited a comment on pull request #34024: [SPARK-36784][SHUFFLE] Handle DNS issues on executor to prevent shuffle nodes from getting added to exclude list

mridulm edited a comment on pull request #34024:
URL: https://github.com/apache/spark/pull/34024#issuecomment-921331388


   I am not sure if we can generalize this expectation - `UnknownHostException` at a node does not imply a local DNS resolution issue alone.
   For example, if a node is decommissioned/removed - fetch failures could result due to `UnknownHostException` as the remote host is no longer resolvable. If we do not trigger a re-execution of the parent stage, tasks in the current stage will keep failing and result in application failure.


-- 
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