Previously, the sniffer functionality was in a separate jar but now it's part of the main Elasticsearch Client jar. As a result, the classpath no longer provides a signal as to whether the sniffer should be auto-configured.
Comment From: anbusampath
Elasticsearch Client's sniffer is an optional feature, can it be disabled by default(currently enabled by default), even though sniffer merged in same rest5 client artifact. Similar discussion happened in 26949
Comment From: wilkinsona
We can consider it, but we'd need a reason to do so. If being enabled by default is causing you a problem, please open a new issue with details of that problem, and ideally a sample that reproduces it, so that we can assess the situation.
Comment From: anbusampath
ideally a sample that reproduces it
I am not sure how to produce sample for this issue. Because this feature was never enabled before in our setup. since it is advised not to enable in certain situation. https://www.elastic.co/blog/elasticsearch-sniffing-best-practices-what-when-why-how.