### Author:  [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)
#### Post date: [May 5, 2016, 7:25am UTC](https://discuss.elastic.co/t/error-unknown-setting-protocol-for-elasticsearch/49264/1 "2016-05-05T07:25:22Z")
Hi,
I have installed **Logstash 2.3.1** and **logstash-output-elasticsearch\_java.gem** because I would like to use the options: protocol, cluster and node\_name in my output. When Logstash starts I receive the next error:
```
{:timestamp=>"2016-05-05T09:11:45.725000+0200", :message=>"Unknown setting 'protocol' for elasticsearch", :level=>:error}
{:timestamp=>"2016-05-05T09:11:45.726000+0200", :message=>"Unknown setting 'cluster' for elasticsearch", :level=>:error}
{:timestamp=>"2016-05-05T09:11:45.729000+0200", :message=>"Pipeline aborted due to error", :exception=>#, :backtrace=>["/soft/sth/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/config/mixin.rb:134:in `config_init'", "/soft/sth/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/outputs/base.rb:63:in `initialize'", "/soft/sth/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/output_delegator.rb:74:in `register'", "/soft/sth/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/pipeline.rb:181:in `start_workers'", "org/jruby/RubyArray.java:1613:in `each'", "/soft/sth/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/pipeline.rb:181:in `start_workers'", "/soft/sth/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/pipeline.rb:136:in `run'", "/soft/sth/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.1-java/lib/logstash/agent.rb:465:in `start_pipeline'"], :level=>:error}
{:timestamp=>"2016-05-05T09:11:48.735000+0200", :message=>"stopping pipeline", :id=>"main"}
```
I know that from **Logstash 2.x** this options are deprecated, however I have seen that with **logstash-output-elasticsearch\_java** I can use them.
Any ideas?
Thanks in advance,
Regards
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [May 5, 2016, 7:26am UTC](https://discuss.elastic.co/t/error-unknown-setting-protocol-for-elasticsearch/49264/2 "2016-05-05T07:26:49Z")
Providing your config would be helpful 🙂
---
### Author:  [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)
#### Post date: [May 5, 2016, 7:29am UTC](https://discuss.elastic.co/t/error-unknown-setting-protocol-for-elasticsearch/49264/3 "2016-05-05T07:29:23Z")
It is a simple configuration:
```
input {
file {
path => "/var/log/messages"
}
}
output {
stdout { codec => rubydebug }
elasticsearch {
hosts => "10.70.64.33"
protocol => "http"
cluster => "test"
}
}
```
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [May 5, 2016, 7:37am UTC](https://discuss.elastic.co/t/error-unknown-setting-protocol-for-elasticsearch/49264/4 "2016-05-05T07:37:39Z")
Per the docs - [https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html) - `protocol` is not a valid setting.
---
### Author:  [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)
#### Post date: [May 5, 2016, 7:47am UTC](https://discuss.elastic.co/t/error-unknown-setting-protocol-for-elasticsearch/49264/5 "2016-05-05T07:47:22Z")
But with **logstash-output-elasticsearch\_java** we can use "protocol" no?
- [https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch\_java.html](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch_java.html)
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [May 5, 2016, 7:47am UTC](https://discuss.elastic.co/t/error-unknown-setting-protocol-for-elasticsearch/49264/6 "2016-05-05T07:47:37Z")
Yes, but you are not using that plugin.
---
### Author:  [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)
#### Post date: [May 5, 2016, 7:57am UTC](https://discuss.elastic.co/t/error-unknown-setting-protocol-for-elasticsearch/49264/7 "2016-05-05T07:57:10Z")
I have installed it with the command (in **Logstash 2.3.1** normal):
> bin/logstash-plugin install logstash-output-elasticsearch\_java-2.1.3.gem
Moreover, I have downloaded **Logstash 2.3.1 All Plugins** , in this version if you see **Gemfile** , you will see:
> gem "logstash-output-elasticsearch\_java"
In both cases it doesn't works.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [May 5, 2016, 8:08am UTC](https://discuss.elastic.co/t/error-unknown-setting-protocol-for-elasticsearch/49264/8 "2016-05-05T08:08:56Z")
I would recommend sticking with the default HTTP protocol. There is a reason support for transport and node mode was moved into a separate plugin. What is it you want to achieve that the HTTP based plugin can not do?
If you still want to use it, you will need to provide some additional details. What does your configuration with elasticsearch\_java plugin look like? What is it that does not work?
---
### Author:  [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)
#### Post date: [May 5, 2016, 8:27am UTC](https://discuss.elastic.co/t/error-unknown-setting-protocol-for-elasticsearch/49264/9 "2016-05-05T08:27:08Z")
I am doing several tests with the options protocol, cluster and node\_name. Now, it works, I made a mistake in a part of my logstash's configuration.
Thanks for all.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 4:59am UTC](https://discuss.elastic.co/t/error-unknown-setting-protocol-for-elasticsearch/49264/10 "2017-07-06T04:59:19Z")