# Upgrading Elasticsearch cluster
**URL:** https://discuss.elastic.co/t/upgrading-elasticsearch-cluster/154726
**Category:** Elasticsearch
**Created:** [October 30, 2018, 9:09pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch-cluster/154726 "2018-10-30T21:09:51Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@lcui\_dxc](https://discuss.elastic.co/u/lcui_dxc)
#### Post date: [October 30, 2018, 9:09pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch-cluster/154726/1 "2018-10-30T21:09:51Z")
Hello there,
We are trying to upgrade our ELK from 6.3.2 to 6.4.2.
It seems we can use rolling upgrades...
The first step would be to disable shard allocation, here we encounter an issue:
here is what I did and got on one of our elasticsearch nodes:
............................
curl -X PUT "[https://elasticnodehost:9200/\_cluster/settings](https://elasticnodehost:9200/_cluster/settings)" -H 'Content-Type: application/json' -d'
{
"persistent": {
"cluster.routing.allocation.enable": "none"
}
}
'
{"error":{"root\_cause":[{"type":"security\_exception","reason":"missing authentication token for REST request [/\_cluster/settings]","header":{"WWW-Authenticate":"Basic realm="security" charset="UTF-8""}}],"type":"security\_exception","reason":"missing authentication token for REST request [/\_cluster/settings]","header":{"WWW-Authenticate":"Basic realm="security" charset=\
....................................
I tried to use -k and --insecure and --cacert options, still the same.
We are using X-Pack (trail version) and the SSL/TLS on all ELK nodes are enabled...
This is no entries in the elasticsearch log at all...
Here is the portion of our elasticsearch.yml with X-Pack enabled:
.............
xpack.monitoring.enabled: true
xpack.monitoring.collection.enabled: true
xpack.monitoring.collection.interval: 60s
xpack.monitoring.collection.cluster.stats.timeout: 60s
xpack.monitoring.history.duration: 90d
xpack.watcher.history.cleaner\_service.enabled: true
xpack.http.proxy.host: '[xxxproxy-01.xxx.yyy.com](http://xxxproxy-01.xxx.yyy.com)'
xpack.http.proxy.port: 3128
xpack.watcher.enabled: true
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification\_mode: certificate
xpack.security.transport.ssl.key: /etc/elasticsearch/keys/xxx-201710-yyy-key.pem
xpack.security.transport.ssl.certificate: /etc/elasticsearch/keys/ServerCertificate.crt
xpack.security.transport.ssl.certificate\_authorities: ["/etc/elasticsearch/keys/ChainBundle2.crt"]
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.verification\_mode: certificate
xpack.security.http.ssl.key: /etc/elasticsearch/keys/xxx-201710-yyy-key.pem
xpack.security.http.ssl.certificate: /etc/elasticsearch/keys/ServerCertificate.crt
xpack.security.http.ssl.certificate\_authorities: ["/etc/elasticsearch/keys/ChainBundle2.crt"]
xpack:
security:
authc:
realms:
active\_directory:
type: active\_directory
order: 0
domain\_name: [xxx.yyy.com](http://xxx.yyy.com)
files.role\_mapping: /etc/elasticsearch/role\_mapping.yml
bind\_dn: CN=yyylocaladmin,CN=Users,DC=xxx,DC=yyy,DC=com
bind\_password: pass
..........................
This is PoC, we are in the process to purchase the 'GOLD' license... but we now need to upgrade to 6.4.1 ASAP.
Please help and let us know how to deal with this...
Thanks a lot in advance
Li
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [October 30, 2018, 9:11pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch-cluster/154726/2 "2018-10-30T21:11:59Z")
You are not passing in any authentication details (user/password) so it's rejecting the request.
---
### Author:  [@lcui\_dxc](https://discuss.elastic.co/u/lcui_dxc)
#### Post date: [October 30, 2018, 9:26pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch-cluster/154726/3 "2018-10-30T21:26:54Z")
I did this:
curl -X PUT -u user1:pass1 "[https://hlsoelke1b-03.hls.dxc.com:9200/\_cluster/settings](https://hlsoelke1b-03.hls.dxc.com:9200/_cluster/settings)" --insecure -H 'Content-Type: application/json' -d'
> {
> "persistent": {
> "cluster.routing.allocation.enable": "none"
> }
> }
> '
> {"acknowledged":true,"persistent":{"cluster":{"routing":{"allocation":{"enable":"none"}}}},"transient":{}}
Does this mean it worked?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [October 30, 2018, 9:34pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch-cluster/154726/4 "2018-10-30T21:34:06Z")
What was the response?
---
### Author:  [@lcui\_dxc](https://discuss.elastic.co/u/lcui_dxc)
#### Post date: [October 30, 2018, 10:22pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch-cluster/154726/5 "2018-10-30T22:22:49Z")
This is the the response:
{"acknowledged":true,"persistent":{"cluster":{"routing":{"allocation":{"enable":"none"}}}},"transient":{}}
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [October 30, 2018, 10:27pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch-cluster/154726/6 "2018-10-30T22:27:21Z")
Then yes, that has worked.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 27, 2018, 10:29pm UTC](https://discuss.elastic.co/t/upgrading-elasticsearch-cluster/154726/7 "2018-11-27T22:29:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.