honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-03-25 09:28:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove outdated DNS caching docs from HTTP exporter (#39394)

Browse Source 
These docs are out of date, now that we override the infinite DNS cache
within Elasticsearch. This commit completely removes this content, as
specific guidance is no longer needed here.
This commit is contained in:
Jason Tedor 2019-02-27 08:08:06 -05:00
parent 842940785a
commit 6c5bf3ac13
No known key found for this signature in database
GPG Key ID: FA89F05560F16BC5
1 changed files with 0 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/reference/monitoring/http-export.asciidoc
View File

@ -91,27 +91,3 @@ monitoring clusters.
For more information about the configuration options for the `http` exporter,
see <<http-exporter-settings>>.
[float]
[[http-exporter-dns]]
==== Using DNS Hosts in HTTP Exporters
{monitoring} runs inside of the JVM security manager. When the JVM has the
security manager enabled, the JVM changes the duration so that it caches DNS
lookups indefinitely (for example, the mapping of a DNS hostname to an IP
address). For this reason, if you are in an environment where the DNS response
might change from time-to-time (for example, talking to any load balanced cloud
provider), you are strongly discouraged from using DNS hostnames.
Alternatively, you can set the JVM security property `networkaddress.cache.ttl`,
which accepts values in seconds. This property must be set for the node's JVM that
uses {monitoring} for {es} when using DNS that can change IP addresses. If you
do not apply this setting, the connection consistently fails after the IP
address changes.
IMPORTANT: JVM security properties are different than system properties. They
cannot be set at startup via `-D` system property settings and instead they must
be set in code before the security manager has been setup _or_, more
appropriately, in the `$JAVA_HOME/lib/security/java.security` file.
Restarting the node (and therefore the JVM) results in its cache being flushed.