Elastic 7.13
I am trying to reduce the indexes we have. One is generated every day going back years, and now we are looking to reduce their number. Reindexing has been suggested, but I cannot get it to work. The reasons are almost certainly the fact that the ILM policy has these as cold. In our ILM managment page I see that the ILM setting for cold is also to freeze the indexes.
Problem: doing a reindex does nothing but return 0 results.
"took" : 0,
"timed_out" : false,
"total" : 0,
"updated" : 0,
"created" : 0,
"deleted" : 0,
"batches" : 0,
"version_conflicts" : 0,
"noops" : 0,
"retries" : {
"bulk" : 0,
"search" : 0
},
"throttled_millis" : 0,
"requests_per_second" : -1.0,
"throttled_until_millis" : 0,
"failures" : [ ]
As stated, this most probably is because the indices are cold and frozen (because our ILM is cold = also frozen)
Unfortunatelly I do not see how to make them writable again. But here is where things get curious and complicated for me. When I ask the settings of the index, I do not see it as frozen, only cold:
"routing" : {
"allocation" : {
"require" : {
"data" : "cold"
}
}
},
Regardless, I did try PUT /_unfreeze but that did not change the re-index result. By definition, the cold index should be writable, unless I'm mistaken. But it's not. And weirder than that, some indices have no setting for "write" but others have this:
"number_of_shards" : "1",
"blocks" : {
"write" : "true"
},
I'm not too sure if this means that the indices without this are NOT writable, or if this is completely different and does not signify that this index can be written in.
Finally, I cannot find a good example in the guides on how to just set an index to a warm state so I can definitely bypass all the other guessing points. Maybe if I knew how to just do that, make the indices warm, I could re-index.
Can anyone help with that? Or am I missing something else as the possible reason reindexing doesn't happen?
