# The Pipeline is Blocked, due to node\_not\_connected\_exception with connection to Data Nodes **URL:** \ **Category:** Logstash\ **Created:** [December 20, 2016, 5:55pm UTC](https://discuss.elastic.co/t/the-pipeline-is-blocked-due-to-node-not-connected-exception-with-connection-to-data-nodes/69602 "2016-12-20T17:55:44Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)\ **Post date:** [December 20, 2016, 8:19pm UTC](https://discuss.elastic.co/t/the-pipeline-is-blocked-due-to-node-not-connected-exception-with-connection-to-data-nodes/69602/2 "2016-12-20T20:19:57Z")
It doesn't appear many folks that have had the same issue are getting much assistance, here's what I've done in order to increase throughput so far (back up to 1800 events/sec from 600, goal is getting back to ~2500); 1. Redirected Logstash output away from the Data Nodes, strictly pointed at client nodes. I wouldn't have thought to direct LS data towards Data Nodes, but it was instructed [elsewhere](https://discuss.elastic.co/t/spikes-in-indexing-rate-methods-to-increase-indexing-rate/68740/4) in the forums. 2. Disable Scatter-Gather on the network cards. As instructed [by other users](https://discuss.elastic.co/t/seeing-frequent-nodenotconnectedexception-errors/21542/4) with the same issue, I disabled this functionality of the network cards. Between these two changes, the indexing rate appears to be getting back up to the typical rate. ![](https://us1.discourse-cdn.com/elastic/original/2X/0/02d84e45161bcb1b4d9c7acbce343441eb932bc3.png) I hope this helps others, please let me know if I missed anything or if you have any additional suggestions. --- _[View the full topic](https://discuss.elastic.co/t/the-pipeline-is-blocked-due-to-node-not-connected-exception-with-connection-to-data-nodes/69602)._