Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Continually try to resolve a host that is unresolved #11256

Closed
wants to merge 1 commit into from

Commits on May 20, 2015

  1. Continually try to resolve a host that is unresolved

    This is a basic fix for the issue described in logstash-plugins/logstash-output-elasticsearch#131
    
    I'm not sure this behaviour is desirable as a default or whether it would make sense to honor Java's networkaddress.cache.ttl and networkaddress.cache.negative.ttl or make ES specific properties.
    slaupster committed May 20, 2015
    Configuration menu
    Copy the full SHA
    6a142c1 View commit details
    Browse the repository at this point in the history