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
Disable reload_connections behavior? #164
Comments
…sport and added unit tests Related: #164
@simpsora Hi, sorry for the delay! The client = Elasticsearch::Client.new reload_connections: false
# ... But I think the code was really confusing in that place, so I've refactored that in the attached commit. Please let me know if you can work with it like this on AWS. Thanks! |
Thanks @karmi! I misread the code there, it makes sense now. I will investigate further and see if setting the parameter to |
@simpsora Great!, let me know when you try it, please. |
@karmi we've now set |
Glad to hear that!
|
Hi,
Is is possible with the gem to entirely disable sniffing /
reload_connections
? I see in base.rb that the config option can either be a number, or 10000 -- there's no way to setfalse
.Use case: we run ES on AWS, and access it through an ELB. We can't access individual machines from the other side of the load balancer, so we want to disable sniffing altogether and force all connections to go via the hostname we give to the client explicitly.
Thanks!
The text was updated successfully, but these errors were encountered: