Hi
I need to remove cold data tiers, then in this action I thought about shifting data tier from cold to warm? How I can handle such case?
is the only one way to re-locate such data index ? when I need to remove data cold?
change from:
{
...
"routing": {
"allocation": {
"include": {
"_tier_preference": "data_cold,data_warm,data_hot"
}
}
}
...
}
PUT /my-index/_settings
{
"routing": {
"allocation": {
"include": {
"_tier_preference": "data_warm,data_hot"
}
}
}
}
Yep, that should work.
and after that I need to reroute that index for relocate?
then I've also triggered
PUT my-index*/_settings
{
"index.routing.allocation.require.data": "warm"
}
but when I'm checking through dev tool
GET /_cat/recovery?active_only=true
It doesn't work as I expected?
for example this index exists on data cold tier
{
"logstash-data-2022.05.14" : {
"settings" : {
"index" : {
"lifecycle" : {
"name" : "data_policy"
},
"routing" : {
"allocation" : {
"include" : {
"_tier_preference" : "data_warm,data_hot"
},
"require" : {
"data" : "warm"
}
}
},
"refresh_interval" : "15s",
"number_of_shards" : "15",
"translog" : {
"sync_interval" : "15s",
"durability" : "async"
},
"provided_name" : "logstash-hss40-2022.05.14",
"creation_date" : "1652486556519",
"priority" : "0",
"number_of_replicas" : "0",
"uuid" : "WtbatoheRgm85R8Ax0hvvg",
"version" : {
"created" : "8010099"
}
}
}
}
}
Are you sure warm is right and not data_warm?
You can check Implementing Hot-Warm-Cold in Elasticsearch with Index Lifecycle Management | Elastic Blog
In this request I’m referring to tier so “warm” “hot” “cold” should be right