# \[SOLVED\] High Network Traffic on Master Nodes after change from Transport Client to REST Client (ElasticSearch 6.8) **URL:** \ **Category:** Elasticsearch\ **Created:** [September 2, 2020, 10:13am UTC](https://discuss.elastic.co/t/solved-high-network-traffic-on-master-nodes-after-change-from-transport-client-to-rest-client-elasticsearch-6-8/247209 "2020-09-02T10:13:24Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![gotenks82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gotenks82/32/74947_2.png) [@gotenks82](https://discuss.elastic.co/u/gotenks82)\ **Post date:** [September 2, 2020, 10:13am UTC](https://discuss.elastic.co/t/solved-high-network-traffic-on-master-nodes-after-change-from-transport-client-to-rest-client-elasticsearch-6-8/247209/1 "2020-09-02T10:13:24Z")
Hi Everyone! We are trying to migrate from the transport client to the high level rest client in our application, but we noticed a strange network load on the master node. Here's our setup: ElasticSearch 6.8 OSS (no x-pack) 3 Master Nodes 49 Data nodes 2 different Indexes with 8 shards and 5 replicas We have a few indexing jobs that run every few minutes, before the migration, using the transport client, the network traffic on master nodes is pretty a flat line, with small changes between 2 and 3 Mbps... using the Rest client, during the indexing, the network traffic on master nodes spikes up to 60 Mbps depending on the job. If I understand correctly, master nodes should not be involved directly in indexing operations, and we verified that we use the SKIP\_DEDICATED\_MASTERS NodeSelectors, and these ARE dedicated masters (no ingest or other roles). The traffic on the DATA nodes, changed from an average of 10 Mbps to an average of 25Mbps during indexing, which I guess can be explained with the change from the binary protocol to the rest json one, and the curves have not changed migrating from one type of client to the other. The client starts with the list of master nodes, uses a sniffer to load the list of data nodes, and then uses the NodeSelector to only cycle in round robin between the data nodes. We are also using the `http.cname_in_publish_address=true` to avoid the warning of deprecation Any idea of what could cause this behavior? ---
**Author:** ![gotenks82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gotenks82/32/74947_2.png) [@gotenks82](https://discuss.elastic.co/u/gotenks82)\ **Post date:** [September 2, 2020, 12:00pm UTC](https://discuss.elastic.co/t/solved-high-network-traffic-on-master-nodes-after-change-from-transport-client-to-rest-client-elasticsearch-6-8/247209/2 "2020-09-02T12:00:49Z")
Hi Guys, sorry we found the cause of the issue 😅 It was a misconfiguration of our client, we had a "conflict" of beans, one was actively using the sniffer to get the data nodes, the other was not, and was simply using the master nodes from configuration. We realized after wards that only part of the code was using the right bean. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [September 2, 2020, 10:21pm UTC](https://discuss.elastic.co/t/solved-high-network-traffic-on-master-nodes-after-change-from-transport-client-to-rest-client-elasticsearch-6-8/247209/3 "2020-09-02T22:21:09Z")
Thanks for sharing your solution 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 30, 2020, 10:21pm UTC](https://discuss.elastic.co/t/solved-high-network-traffic-on-master-nodes-after-change-from-transport-client-to-rest-client-elasticsearch-6-8/247209/4 "2020-09-30T22:21:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.