Clean up Opensearch documentation on zero downtime #6475
Description
What we’re after
The zero downtime deployment documentation should be cleaned up.
Is the zero downtime option actually zero downtime? It's the same function used in the downtime just without recreating the index
My current understanding is that we don't have memory to support the low downtime options because case_index is so large. We should confirm this and then consider breaking down this index so that we could use a low downtime solution.
We should make the docs more clear and create tickets to start this work
Related ticket(s)
(Include the tickets that either came before, after, or are happening in tandem with this new ticket)
- [ ]
Action item(s)
(These are the smaller tasks that should happen in order to complete this work)
- [ ]
Completion criteria
(What does the end state look like - as long as this task(s) is done, this work is complete)
- [ ]
References/resources/technical considerations
(Is there sample code or a screenshot you can include to highlight a particular issue? Here is where you reinforce why this work is important)