# Does logstash 2.2.2-1 has backward compatibility with ES-1.5?

**URL:** <https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158>\
**Category:** Logstash\
**Created:** [March 1, 2016, 9:11pm UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158 "2016-03-01T21:11:12Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![piyush](https://avatars.discourse-cdn.com/v4/letter/p/ecb155/32.png) [@piyush](https://discuss.elastic.co/u/piyush)\
**Post date:** [March 1, 2016, 9:11pm UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158/1 "2016-03-01T21:11:12Z")

</div>

Hi,  
I installed logstash-2.2.2-1.noarch.rpm and trying to connect managed Elastic Search cluster (version: 1.5.2), it failing with error:  
[408] {:class=\>"Elasticsearch::Transport::Transport::Errors::RequestTimeout", :level=\>:error}

\*i verified with curl -XGET and cluster is reachable from instance.

Log file indicates that logstash is looking for ES 2.5.1?

From log:  
elasticsearch-transport-1.0.15  
logstash-output-elasticsearch-2.5.1-java

Please confirm if logstash2.2.2-1 can connect to ES-1.5.2

Regards...

---

<div class="post-metadata">

**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:** [March 1, 2016, 9:13pm UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158/2 "2016-03-01T21:13:01Z")

</div>

Yes, but use the HTTP protocol, not transport.

---

<div class="post-metadata">

**Author:** ![piyush](https://avatars.discourse-cdn.com/v4/letter/p/ecb155/32.png) [@piyush](https://discuss.elastic.co/u/piyush)\
**Post date:** [March 1, 2016, 9:15pm UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158/3 "2016-03-01T21:15:27Z")

</div>

Thanks, let me give that a try.

---

<div class="post-metadata">

**Author:** ![piyush](https://avatars.discourse-cdn.com/v4/letter/p/ecb155/32.png) [@piyush](https://discuss.elastic.co/u/piyush)\
**Post date:** [March 1, 2016, 9:25pm UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158/4 "2016-03-01T21:25:14Z")

</div>

output {  
elasticsearch  
{  
hosts =\> "xyz"  
protocol =\> "http"  
}  
}

It's an error:  
Unknown setting 'protocol' for elasticsearch {:level=\>:error}

---

<div class="post-metadata">

**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:** [March 1, 2016, 9:26pm UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158/5 "2016-03-01T21:26:26Z")

</div>

Oh, remove the protocol part and you should be good.

---

<div class="post-metadata">

**Author:** ![piyush](https://avatars.discourse-cdn.com/v4/letter/p/ecb155/32.png) [@piyush](https://discuss.elastic.co/u/piyush)\
**Post date:** [March 1, 2016, 9:29pm UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158/6 "2016-03-01T21:29:08Z")

</div>

Nup, then it will through that transport error, earlier i was not using protocol.

---

<div class="post-metadata">

**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:** [March 1, 2016, 9:31pm UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158/7 "2016-03-01T21:31:24Z")

</div>

If you're on LS 2.X, using the `elasticsearch` output defaults to HTTP.  
I'd remove the `logstash-output-elasticsearch-2.5.1-java` plugin.

---

<div class="post-metadata">

**Author:** ![piyush](https://avatars.discourse-cdn.com/v4/letter/p/ecb155/32.png) [@piyush](https://discuss.elastic.co/u/piyush)\
**Post date:** [March 1, 2016, 9:35pm UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158/8 "2016-03-01T21:35:52Z")

</div>

Ok, let me try that.  
BTW, i tried [http://xyz](http://xyz) as my ES (instead of https) and it threw an exception  
exception (org.apache.http.NoHttpResponseException)

But this time i know the reason, logstash added port 80 by default. and it won't work in my case.

Regards...

---

<div class="post-metadata">

**Author:** ![piyush](https://avatars.discourse-cdn.com/v4/letter/p/ecb155/32.png) [@piyush](https://discuss.elastic.co/u/piyush)\
**Post date:** [March 1, 2016, 9:45pm UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158/9 "2016-03-01T21:45:34Z")

</div>

I guess it was not using the plugin.

/opt/logstash/bin/plugin uninstall logstash-output-elasticsearch-2.5.1-java  
ERROR: Uninstall Aborted, message: This plugin has not been previously installed, aborting

what else i can try?

Regards...

---

<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 6, 2017, 5:09am UTC](https://discuss.elastic.co/t/does-logstash-2-2-2-1-has-backward-compatibility-with-es-1-5/43158/10 "2017-07-06T05:09:00Z")

</div>