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
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. 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.
Daniel