You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (JIRA)" <ji...@apache.org> on 2019/07/16 16:42:13 UTC
[jira] [Updated] (SPARK-28149) Disable negeative DNS caching
[ https://issues.apache.org/jira/browse/SPARK-28149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun updated SPARK-28149:
----------------------------------
Affects Version/s: (was: 2.4.3)
3.0.0
> Disable negeative DNS caching
> -----------------------------
>
> Key: SPARK-28149
> URL: https://issues.apache.org/jira/browse/SPARK-28149
> Project: Spark
> Issue Type: Improvement
> Components: Kubernetes
> Affects Versions: 3.0.0
> Reporter: Jose Luis Pedrosa
> Priority: Minor
>
> By default JVM caches the failures for the DNS resolutions, by default is cached by 10 seconds.
> Alpine JDK used in the images for kubernetes has a default timout of 5 seconds.
> This means that in clusters with slow init time (network sidecar pods, slow network start up) executor will never run, because the first attempt to connect to the driver will fail, and that failure will be cached, causing the retries to happen in a tight loop without actually trying again.
>
> The proposed implementation would be to add to the entrypoint.sh (that is exclusive for k8s) to alter the file with the dns caching, and disable it if there's an environment variable as "DISABLE_DNS_NEGATIVE_CACHING" defined.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org