Changelog for Instructions to Reindex Indexes #6151
Conversation
| - If you have sepearate data nodes, check disk usage on data nodes | ||
| ```sh | ||
| cchq <env> run-shell-command es_data "df -h /opt/data" -b | ||
| ``` | ||
| - If you don't have separate data nodes, check disk usage on ES nodes. | ||
| ```sh | ||
| cchq <env> run-shell-command es_data "df -h /opt/data" -b | ||
| ``` |
There was a problem hiding this comment.
The commands in these two points are identical. If that was expected, would it be possible to combine the two points into one?
There was a problem hiding this comment.
Nope. It should have been
cchq <env> run-shell-command elasticsearch "df -h /opt/data" -bThere was a problem hiding this comment.
|
|
||
| 3. Verify reindex is completed by querying the logs and ensuring that doc count matches between primary and secondary indices. The commands in this step should be run from control machine. | ||
|
|
||
| 1. In a new shell login to control machine. |
There was a problem hiding this comment.
| 1. In a new shell login to control machine. | |
| 1. Login to the control machine in a new shell. |
Also, formatting of this sub-list does not seem to be rendering correctly on github. It's rendering as a fixed-width code block, which might mean it's indented too far?
There was a problem hiding this comment.
Fixed the formatting in 65ed26f
Co-authored-by: Daniel Miller <[email protected]>
| @@ -0,0 +1,85 @@ | |||
| title: reindex-all-indexes-for-es-upgrade | |||
There was a problem hiding this comment.
nit: I think the title field can be more "human readable" right?
There was a problem hiding this comment.
I thought this is what is used in urls but I realised now that we have key for that. Fixed in 75743be
| [2023-10-25 08:59:37,648][INFO] [tasks] 29216 finished with response ReindexResponse[took=1.8s,updated=0,created=1111,batches=2,versionConflicts=0,noops=0,retries=0,throttledUntil=0s,indexing_failures=[],search_failures=[]] | ||
| ``` | ||
|
|
||
| Ensure that `search_failures` and `indexing_failures` are empty lists. |
There was a problem hiding this comment.
Just a thought, but what should they do if either of these are not empty lists?
There was a problem hiding this comment.
Ahh! I missed it, thanks for catching that - added in a47409d
|
|
||
| If reindex fails for any index, please refer to the docs [here](https://github.com/dimagi/commcare-hq/blob/56682492f20c60cdef0ccde6049b9945b3658493/corehq/apps/es/REINDEX_PROCESS.md#common-issues-resolutions-during-reindex) for troubleshooting steps. | ||
|
|
||
| 4. If doc counts match and there are no errors present in the reindex logs, the reindex for the current index is complete. You can continue reindexing for the next index by repeating steps 5.1-5.3 with `${INDEX_CNAME}` set to 'cases', 'case_search' and so on for all indices. |
Changelog for steps to reindex the ES indices.
Environments Affected
All
Announce New Release
to announce a new commcare-cloud release.