We're testing out marvel and noticed that it causes failures unless HTTP is
enabled for the node. This isn't ideal for data nodes that we've disabled
HTTP on.
Is this just "the way things work" or is there an alternative I'm not aware
of?
It's not a big deal, but does means we can't use the Sniffing Connection
Pool that some clients support because it round robins across all nodes
capable of HTTP traffic.
Thanks,
--
Nick Canzoneri
Developer, Wildbit http://wildbit.com/
Beanstalk http://beanstalkapp.com/, Postmark http://postmarkapp.com/,
dploy.io
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKWm5yMtDHLFsOXPagxH4J0fsxFXpOYOhV7XkqSsChwVHnaydg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.