# River puts too much load on only one node

**URL:** <https://discuss.elastic.co/t/river-puts-too-much-load-on-only-one-node/180053>\
**Category:** Elasticsearch\
**Created:** [May 7, 2019, 7:52pm UTC](https://discuss.elastic.co/t/river-puts-too-much-load-on-only-one-node/180053 "2019-05-07T19:52:57Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![KashiPashoria\_Tonny](https://avatars.discourse-cdn.com/v4/letter/k/d07c76/32.png) [@KashiPashoria\_Tonny](https://discuss.elastic.co/u/KashiPashoria_Tonny)\
**Post date:** [May 8, 2019, 7:39am UTC](https://discuss.elastic.co/t/river-puts-too-much-load-on-only-one-node/180053/11 "2019-05-08T07:39:20Z")

</div>

> [@Can not convert from long to float logstash](https://discuss.elastic.co/t/can-not-convert-from-long-to-float-logstash/168577):
>
> I'm taking data from sql server to elasticsearch 6.6 using logstash and jdbc. Some of my records are skipped by logstash printing these warning logs: [2019-02-15T16:48:52,630][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>"2111348540", :\_index=\>"order\_tracking1", :\_type=\>"orderstracking\_report", :\_routing=\>nil}, #LogStash::Event:0x14b8bcd8], :response=\>{"index"=\>{"\_index"=\>"order\_tracking1", "\_type"=\>"orderstracking\_repor…

its the issue with logstash I posted when I was using it a couple of months ago and it went unsolved. However, I can't now move back to logstash.

---

_[View the full topic](https://discuss.elastic.co/t/river-puts-too-much-load-on-only-one-node/180053)._