Deploy fix to search and reindex
kilbergr opened this issue · 0 comments
kilbergr commented
We resolved this issue--yay!
However, its resolution requires running the rebuild_search_index fab command in order to reindex the CaseDocuments with the new field configuration. Two issues spill out of that:
- We'd have to take the app offline to do this work. Instead, Ben has a parallel deployment process where you deploy to a "beta branch" and then switch it out with the original running instance. He has to remember how this works.
- We don't know how much space the new index would take. We'd like to find out by how much so that we don't outstrip the disk space allocated on prod. This thread is being discussed in the PR for the issue.
- Possible thread: We could try using the reindex API with copy to index in a different location and see how big that is while maintaining the old index. I don't think that really gets at the issue though because if one index might be too big, two certainly are. Unless we do something like intentionally increase disk space beyond what we'll need, run the reindex in a copy, compare, resize. But if we do that, we may as well just do that without copying it.
This issue is to complete the work above. Once it's done, we can deploy this PR.
- Possible thread: We could try using the reindex API with copy to index in a different location and see how big that is while maintaining the old index. I don't think that really gets at the issue though because if one index might be too big, two certainly are. Unless we do something like intentionally increase disk space beyond what we'll need, run the reindex in a copy, compare, resize. But if we do that, we may as well just do that without copying it.