Dear Community,
I am in the process of performing a shrink on indices in order to reduce the number of shards from 5 to 1 , i choose to test on my cluster on 1 index named "logstash-ssh-*'
So i followed the documentation form elasticsearch : https://www.elastic.co/guide/en/elasticsearch/reference/6.2/indices-shrink-index.html
By putting index in read-only and relocating the shards to one node in order to have the primary and replica on the same elasticsearch node.
PUT /logstash-ssh-*/_settings
{
"settings": {
"index.routing.allocation.require._host": "elastic-01",
"index.blocks.write": true
}
}
If I check if the operation has been taken by elasticsearch it seems yes :
"logstash-ssh-2018.05.15": {
"settings": {
"index": {
"blocks": {
"write": "true"
},
"creation_date": "1526342499442",
"number_of_replicas": "1",
"number_of_shards": "5",
"provided_name": "logstash-ssh-2018.05.15",
"refresh_interval": "5s",
"routing": {
"allocation": {
"require": {
"_host": "",
"_ip": "",
"_name": "elastic-01"
}
}
},
"uuid": "Lq38GrBySk6qO2RNRa8Clw",
"version": {
"created": "6020399"
}
}
}
},
.....
But when I check if somes shards are relocating , it seems not
curl -s 'http://elastic-01.domain.local:9200/_cat/shards?v' | fgrep RELO
<Empty output>
And if i check the shards by filtering from the index pattern logstash-ssh-*, it seems that nothing happen , the shards are still shared with my both elasticsearch nodes.
Did i miss something , is there are some parameter that stuck relocating of shards at the cluster level ?
I'm running the 6.2.3 Elasticsearch version on my cluster.
Thanks in advance for your help.
Best Regards, Edouard Fazenda.