# Getting errors after upgrading logstash version from 1.5.3 to 2.3.3
**URL:** https://discuss.elastic.co/t/getting-errors-after-upgrading-logstash-version-from-1-5-3-to-2-3-3/55274
**Category:** Logstash
**Created:** [July 12, 2016, 9:05am UTC](https://discuss.elastic.co/t/getting-errors-after-upgrading-logstash-version-from-1-5-3-to-2-3-3/55274 "2016-07-12T09:05:47Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@gayathri](https://discuss.elastic.co/u/gayathri)
#### Post date: [July 12, 2016, 9:05am UTC](https://discuss.elastic.co/t/getting-errors-after-upgrading-logstash-version-from-1-5-3-to-2-3-3/55274/1 "2016-07-12T09:05:47Z")
Hi Team,
I have upgraded Logstash version from 1.5.3 to 2.3.3, On logstash debug getting below errors:
Unknown setting 'cluster' for elasticsearch {:level=\>:error, :file=\>"logstash/config/mixin.rb", :line=\>"329", :method=\>"validate\_check\_invalid\_parameter\_names"}
Unknown setting 'protocol' for elasticsearch {:level=\>:error, :file=\>"logstash/config/mixin.rb", :line=\>"329", :method=\>"validate\_check\_invalid\_parameter\_names"}
How can i set clustername in logstash then?
Thanks,
gayathri
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [July 12, 2016, 11:09am UTC](https://discuss.elastic.co/t/getting-errors-after-upgrading-logstash-version-from-1-5-3-to-2-3-3/55274/2 "2016-07-12T11:09:13Z")
The elasticsearch output in Logstash 2.0 and later only supports HTTP which explains the complaint about the `protocol` option, and with HTTP the cluster name is irrelevant which explains the demise of the `cluster` option.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 4:48am UTC](https://discuss.elastic.co/t/getting-errors-after-upgrading-logstash-version-from-1-5-3-to-2-3-3/55274/3 "2017-07-06T04:48:27Z")