# Inconsistency: input elasticsearch does not require "cluster" but output elastic search requires it

**URL:** https://discuss.elastic.co/t/inconsistency-input-elasticsearch-does-not-require-cluster-but-output-elastic-search-requires-it/1520
**Category:** Logstash
**Created:** [May 28, 2015, 9:45pm UTC](https://discuss.elastic.co/t/inconsistency-input-elasticsearch-does-not-require-cluster-but-output-elastic-search-requires-it/1520 "2015-05-28T21:45:25Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![discuss03](https://avatars.discourse-cdn.com/v4/letter/d/9fc348/32.png) [@discuss03](https://discuss.elastic.co/u/discuss03)
#### Post date: [May 28, 2015, 9:45pm UTC](https://discuss.elastic.co/t/inconsistency-input-elasticsearch-does-not-require-cluster-but-output-elastic-search-requires-it/1520/1 "2015-05-28T21:45:25Z")

</div>

There seems to be a inconsistency between the input and output versions for logstash elasticsearch.

Input elastic search does not understand the parameter "host" even though it is documented on the website. Input elasticsearch does not require to specify the "cluster" parameter to read events even though it is not the default one.

Output elasticsearch requires the "cluster" parameter when writing to elasticsearch.

Any ideas if these are bugs, or is this how it is designed to be? It would also be nice if the documentation went a bit further with cases...

Is there a place that shows samples of other peoples logstash configurations - like:

Read from Elasticsearch  
Filter using GROK  
Write to Elasticsearch

---

<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: [May 29, 2015, 2:20am UTC](https://discuss.elastic.co/t/inconsistency-input-elasticsearch-does-not-require-cluster-but-output-elastic-search-requires-it/1520/2 "2015-05-29T02:20:57Z")

</div>

What version are you using?

---

<div class="post-metadata">

### Author: ![discuss03](https://avatars.discourse-cdn.com/v4/letter/d/9fc348/32.png) [@discuss03](https://discuss.elastic.co/u/discuss03)
#### Post date: [May 29, 2015, 6:16am UTC](https://discuss.elastic.co/t/inconsistency-input-elasticsearch-does-not-require-cluster-but-output-elastic-search-requires-it/1520/3 "2015-05-29T06:16:16Z")

</div>

The latest

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [May 29, 2015, 7:05am UTC](https://discuss.elastic.co/t/inconsistency-input-elasticsearch-does-not-require-cluster-but-output-elastic-search-requires-it/1520/4 "2015-05-29T07:05:29Z")

</div>

> The latest

Please be explicit. We can't know which version _you_ think is the latest.

The Logstash 1.5.0 documentation does talk about a `host` parameter in the examples but the actual (and documented) parameter name is `hosts`. This is a documentation bug that's fixed here:

> <https://github.com/logstash-plugins/logstash-input-elasticsearch/pull/17>
>
> removes port setting since you can specify host:port in the "hosts" config param…eter
> 
> addresses #16

---

<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:39am UTC](https://discuss.elastic.co/t/inconsistency-input-elasticsearch-does-not-require-cluster-but-output-elastic-search-requires-it/1520/5 "2017-07-06T05:39:06Z")

</div>


