# Error sending bulk request do Elasticsearch **URL:** \ **Category:** Logstash\ **Created:** [May 28, 2019, 8:49pm UTC](https://discuss.elastic.co/t/error-sending-bulk-request-do-elasticsearch/183193 "2019-05-28T20:49:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![luisdiasbh](https://avatars.discourse-cdn.com/v4/letter/l/eb9ed0/32.png) [@luisdiasbh](https://discuss.elastic.co/u/luisdiasbh)\ **Post date:** [May 28, 2019, 8:49pm UTC](https://discuss.elastic.co/t/error-sending-bulk-request-do-elasticsearch/183193/1 "2019-05-28T20:49:39Z")
I'm able to read some data from hive table throught jdbc connection but when it will be inserted on elastic i have the following error: > [ERROR] 2019-05-28 17:39:36.643 [[main]\>worker1] elasticsearch - An unknown error occurred sending a bulk request to Elasticsearch. We will retry indefinitely {:error\_message=\>"no method 'setHeaders' for arguments (org.jruby.java.proxies.ArrayJavaProxy) on Java::OrgApacheHttpClientMethods::HttpPost\n available overloads:\n (org.apache.http.Header)\n (org.apache.http.Header)", :error\_class=\>"NameError", :backtrace=\>["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/manticore-0.6.4-java/lib/manticore/client.rb:504:in `request_from_options'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/manticore-0.6.4-java/lib/manticore/client.rb:421:in `request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/manticore-0.6.4-java/lib/manticore/client.rb:266:in `post'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/manticore_adapter.rb:69:in `perform\_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:291:in `perform_request_to_url'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:278:in `block in perform\_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:373:in `with_connection'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:277:in `perform\_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:285:in `block in Pool'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client.rb:143:in `bulk\_send'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http\_client.rb:128:in `bulk'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/common.rb:296:in `safe\_bulk'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/common.rb:201:in `submit'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/common.rb:169:in `retrying\_submit'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/common.rb:38:in `multi_receive'", "org/logstash/config/ir/compiler/OutputStrategyExt.java:118:in `multi\_receive'", "org/logstash/config/ir/compiler/AbstractOutputDelegatorExt.java:101:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:235:in `block in start\_workers'"]} Im using elastic 7.1.1 with logstash 7.1.1. Anyone know what are happening? ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [May 28, 2019, 9:46pm UTC](https://discuss.elastic.co/t/error-sending-bulk-request-do-elasticsearch/183193/2 "2019-05-28T21:46:40Z")
Which version of Java? What does the elasticsearch output configuration look like? ---
**Author:** ![luisdiasbh](https://avatars.discourse-cdn.com/v4/letter/l/eb9ed0/32.png) [@luisdiasbh](https://discuss.elastic.co/u/luisdiasbh)\ **Post date:** [May 28, 2019, 11:05pm UTC](https://discuss.elastic.co/t/error-sending-bulk-request-do-elasticsearch/183193/3 "2019-05-28T23:05:27Z")
output config: output { elasticsearch { index =\> "hive" hosts =\> ["127.0.0.1"] } } java: openjdk version "1.8.0\_181" OpenJDK Runtime Environment (build 1.8.0\_181-b13) OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode) Shoud i upgrade to Java 11? ---
**Author:** ![NickBook](https://avatars.discourse-cdn.com/v4/letter/n/cab0a1/32.png) [@NickBook](https://discuss.elastic.co/u/NickBook)\ **Post date:** [June 18, 2019, 2:54pm UTC](https://discuss.elastic.co/t/error-sending-bulk-request-do-elasticsearch/183193/4 "2019-06-18T14:54:18Z")
I'm experiencing the same error described by luisdiasbh using the JDBC input plugin with Hive-2.1 JDBC drivers. My config file, which has been working in Logstash 6.0, is not working with Logstash 7.0 or Logstash 7.1 running on JDK 1.8.0\_XXX. I am also using Elasticsearch 7.1, which works fine with my config file in Logstash 6.0 but not 7.0. In Logstash 7.0 and 7.1, I can see my input in the rubydebug output codec, so my Hive JDBC driver and connection string is working, just not interacting nicely with Elasticsearch. Any suggestions or insights to something that got changed in Logstash 7.0 that may cause this? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 16, 2019, 3:06pm UTC](https://discuss.elastic.co/t/error-sending-bulk-request-do-elasticsearch/183193/5 "2019-07-16T15:06:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.