venkata91 edited a comment on pull request #34024: URL: https://github.com/apache/spark/pull/34024#issuecomment-930393628
> We first check if some other "known good" hostname is resolvable, as defined by spark.network.dnsHealthCheck.host, and only if that host isn't resolvable, we assume there is a local DNS issue. @xkrogen The problem with this solution is the heavy DNS caching happening at JVM, N/W layers etc which makes this very brittle. Also the case of decommissioning needs to be thought through further. But the overall idea still seems relevant to me with a modified approach (mainly resolving DNS of remote host without hitting the cache). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
