dns-cache.asciidoc 1.2 KB

12345678910111213141516171819
  1. [[networkaddress-cache-ttl]]
  2. === DNS cache settings
  3. Elasticsearch runs with a security manager in place. With a security manager in
  4. place, the JVM defaults to caching positive hostname resolutions indefinitely
  5. and defaults to caching negative hostname resolutions for ten
  6. seconds. Elasticsearch overrides this behavior with default values to cache
  7. positive lookups for sixty seconds, and to cache negative lookups for ten
  8. seconds. These values should be suitable for most environments, including
  9. environments where DNS resolutions vary with time. If not, you can edit the
  10. values `es.networkaddress.cache.ttl` and `es.networkaddress.cache.negative.ttl`
  11. in the <<jvm-options,JVM options>>. Note that the values
  12. http://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html[`networkaddress.cache.ttl=<timeout>`]
  13. and
  14. http://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html[`networkaddress.cache.negative.ttl=<timeout>`]
  15. in the
  16. http://docs.oracle.com/javase/8/docs/technotes/guides/security/PolicyFiles.html[Java
  17. security policy] are ignored by Elasticsearch unless you remove the settings for
  18. `es.networkaddress.cache.ttl` and `es.networkaddress.cache.negative.ttl`.