From 2517a9879ec5f4e6816b2329f17ca394f0ac393f Mon Sep 17 00:00:00 2001 From: Siegfried Weber Date: Mon, 7 Oct 2024 11:41:24 +0200 Subject: [PATCH] Improve wording Co-authored-by: Andrew Kenworthy <1712947+adwk67@users.noreply.github.com> --- .../pages/usage-guide/configuration-environment-overrides.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/spark-k8s/pages/usage-guide/configuration-environment-overrides.adoc b/docs/modules/spark-k8s/pages/usage-guide/configuration-environment-overrides.adoc index 065a1446..140baa66 100644 --- a/docs/modules/spark-k8s/pages/usage-guide/configuration-environment-overrides.adoc +++ b/docs/modules/spark-k8s/pages/usage-guide/configuration-environment-overrides.adoc @@ -80,7 +80,7 @@ The `security.properties` file is used to configure JVM security properties. It is very seldom that users need to tweak any of these, but there is one use-case that stands out, and that users need to be aware of: the JVM DNS cache. The JVM manages its own cache of successfully resolved host names as well as a cache of host names that cannot be resolved. -Some products of the Stackable platform are very sensible to the contents of these caches and their performance is heavily affected by them. +Some products of the Stackable platform are very sensitive to the contents of these caches and their performance is heavily affected by them. As of version 3.4.0, Apache Spark may perform poorly if the positive cache is disabled. To cache resolved host names, and thus speeding up queries you can configure the TTL of entries in the positive cache like this: