# Elastic 5.0.0-alpha3 issues with some settings

**URL:** <https://discuss.elastic.co/t/elastic-5-0-0-alpha3-issues-with-some-settings/52619>\
**Category:** Elasticsearch\
**Created:** [June 13, 2016, 2:00pm UTC](https://discuss.elastic.co/t/elastic-5-0-0-alpha3-issues-with-some-settings/52619 "2016-06-13T14:00:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tikkisetty](https://avatars.discourse-cdn.com/v4/letter/t/aeb1de/32.png) [@tikkisetty](https://discuss.elastic.co/u/tikkisetty)\
**Post date:** [June 13, 2016, 2:00pm UTC](https://discuss.elastic.co/t/elastic-5-0-0-alpha3-issues-with-some-settings/52619/1 "2016-06-13T14:00:04Z")

</div>

After upgrade of elastic from 2.3.1 to 5.0.0-alpha3 , i had to remove/comment out the parameters

http.jsonp.enable (error: unknown setting [http.jsonp.enable] did you mean [http.cors.enabled]?)  
node.rack ( not a valid setting)  
bootstrap.mlockall ( error : memory locking requested for elasticsearch process but memory is not locked))

in the elasticsearch.yml config file.

However, requests to elastic cluster are failing with error- Error: connect ECONNREFUSED - when tried to copy an index to elastic from another cluster using elasticdump. Please suggest

---

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [June 14, 2016, 9:21am UTC](https://discuss.elastic.co/t/elastic-5-0-0-alpha3-issues-with-some-settings/52619/2 "2016-06-14T09:21:22Z")

</div>

Hi @tikkisetty,

the error message indicates that your cluster is not reachable. Did it start correctly? You can easily check this by running `curl 'http://your-cluster-ip:9200'`. It should return basic information about the cluster. If not, please check the logs.

To the other errors:

> http.jsonp.enable (error: unknown setting [http.jsonp.enable] did you mean [http.cors.enabled]?)  
> node.rack ( not a valid setting)

This setting is [not valid since Elasticsearch 2.0](https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_setting_changes.html#_jsonp_support). In 5.0 we have added checks that do not allow any unknown settings. That's why it shows up now.

> bootstrap.mlockall ( error : memory locking requested for elasticsearch process but memory is not locked))

You can check the guide [enable memory locking](https://www.elastic.co/guide/en/elasticsearch/reference/master/setup-configuration-memory.html#mlockall).

Daniel

---

<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 5, 2017, 10:44pm UTC](https://discuss.elastic.co/t/elastic-5-0-0-alpha3-issues-with-some-settings/52619/3 "2017-07-05T22:44:00Z")

</div>