# Elasticsearch.net 5.0 Beta1, SniffingConnectionPool - Failed sniffing cluster state

**URL:** <https://discuss.elastic.co/t/elasticsearch-net-5-0-beta1-sniffingconnectionpool-failed-sniffing-cluster-state/63874>\
**Category:** Elasticsearch\
**Created:** [October 25, 2016, 1:23pm UTC](https://discuss.elastic.co/t/elasticsearch-net-5-0-beta1-sniffingconnectionpool-failed-sniffing-cluster-state/63874 "2016-10-25T13:23:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![murfee25](https://avatars.discourse-cdn.com/v4/letter/m/b487fb/32.png) [@murfee25](https://discuss.elastic.co/u/murfee25)\
**Post date:** [October 25, 2016, 1:23pm UTC](https://discuss.elastic.co/t/elasticsearch-net-5-0-beta1-sniffingconnectionpool-failed-sniffing-cluster-state/63874/1 "2016-10-25T13:23:52Z")

</div>

Not sure if this is the correct forum, but I had this working last week but for the life of me I can't get it to work this week.

Question: Is the SniffingConnectionPool currently supported by the [Elasticsearch.net/NEST](http://Elasticsearch.net/NEST) APIs ?

2 nodes running ES 5.0.0-rc1, on my windows machine, another node on another developers windows machine.

Running these statements from Linqpad:

```
var nodes = new List<string>(){"http://danny-desktop:9200", "http://danny-desktop:9201", "http://vinay-desktop:9200"};

var uris = nodes.Select(n=> new Uri(n));
var connectionPool = new SniffingConnectionPool(uris);
//var connectionPool = new StickyConnectionPool(uris);

var connectionSettings = new ConnectionSettings(connectionPool);

var client = new ElasticClient(connectionSettings);

var result = client.IndexExists(Indices.Parse("hd20160518"));

result.Dump();

```

It fails with message "Failed sniffing cluster state." Inner exception stack trace places it at:

```
at Elasticsearch.Net.Node..ctor(Uri uri)
at Elasticsearch.Net.SniffResponse.<ToNodes>d__11.MoveNext()
at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source)
at Elasticsearch.Net.SniffingConnectionPool.Reseed(IEnumerable`1 nodes)
at Elasticsearch.Net.RequestPipeline.Sniff()

```

It looks to me like the code is expecting to find a property "http\_address" on the result of the request for:

```
_nodes/_all/settings?flat_settings&timeout=2s

```

Previous versions (1.7 and 2.4) return this property.

any help/advise greatly appreciated.

regards,  
Danny

---

<div class="post-metadata">

**Author:** ![gmarz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gmarz/32/22178_2.png) [@gmarz](https://discuss.elastic.co/u/gmarz)\
**Post date:** [October 25, 2016, 6:21pm UTC](https://discuss.elastic.co/t/elasticsearch-net-5-0-beta1-sniffingconnectionpool-failed-sniffing-cluster-state/63874/2 "2016-10-25T18:21:49Z")

</div>

Hi murfee25, thanks for reporting this, it's definitely a bug in the client due to changes in the nodes API response. I've opened [https://github.com/elastic/elasticsearch-net/issues/2339](https://github.com/elastic/elasticsearch-net/issues/2339) to track this, and we're working on a fix for the next release.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:09pm UTC](https://discuss.elastic.co/t/elasticsearch-net-5-0-beta1-sniffingconnectionpool-failed-sniffing-cluster-state/63874/3 "2017-07-05T22:09:50Z")

</div>