Remove the ability to read frozen indices #120108
Conversation
This won't be supported in 9.0. In 8.18+ we report a `CRITICAL` deprecation warning telling users to unfreeze any frozen indices (see elastic#119879).
PeteGillinElastic force-pushed the frozen-indices-unregister-engine branch from 312499f to c300f63 Compare PeteGillinElastic added >breaking :Data Management/Indices APIs 
| Hi @PeteGillinElastic, I've created a changelog YAML for you. Note that since this PR is labelled |
PeteGillinElastic changed the title FrozenEngine in plugin
elasticsearchmachine added the Team:Data Management | Pinging @elastic/es-data-management (Team:Data Management) |
| @PeteGillinElastic is this PR relevant to the serverless changelog? [FYI this question is based on 9.0 breaking changes] |
No, frozen indices were never a thing in serverless. |
| @PeteGillinElastic does this affect snapshots of indices mounted on frozen tier as well? Is frozen tier still usable in version 9? If snapshots are still usable what is the difference between this and "frozen indices"? |
| Sorry, only just saw this. Yeah, for the avoidance of doubt, this is nothing to do with the frozen tier, which is still a supported feature that we recommend using where appropriate. Older versions of ES had an unrelated feature with an unfortunately similar name, frozen indices. This PR is about removal some remnants of that feature. |
| (In case you're curious: The old 'frozen indices' feature was about reducing the memory usage for rarely-used indices. It was removed because it stopped providing significant benefit due to other improvements in ES.) |
5 participants
This won't be supported in 9.0. In 8.18+ we report a
CRITICALdeprecation warning telling users to unfreeze any frozen indices (see #119879).