diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-30 09:07:11 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-30 09:07:11 +0300 |
| commit | bb1221318722595bcf917354f9d29621ca7413d5 (patch) | |
| tree | 37eb1ba5d248062c641177f1a7a19b4e9d2e6241 /doc/integration | |
| parent | f3baa9145d2e41f30c9f24669c06b39e283fb499 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/integration')
| -rw-r--r-- | doc/integration/advanced_search/elasticsearch_troubleshooting.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/integration/advanced_search/elasticsearch_troubleshooting.md b/doc/integration/advanced_search/elasticsearch_troubleshooting.md index d13d47a1633..df1e1f49083 100644 --- a/doc/integration/advanced_search/elasticsearch_troubleshooting.md +++ b/doc/integration/advanced_search/elasticsearch_troubleshooting.md @@ -513,3 +513,9 @@ $ jq '.class' sidekiq/current | sort | uniq -c | sort -nr In this case, `free -m` on the overloaded GitLab node would also show unexpectedly high `buff/cache` usage. + +## `Couldn't load task status` error when reindexing + +When you reindex, you might get a `Couldn't load task status` error. A `sliceId must be greater than 0 but was [-1]` error might also appear on the Elasticsearch host. As a workaround, consider [reindexing from scratch](../../integration/advanced_search/elasticsearch_troubleshooting.md#last-resort-to-recreate-an-index) or upgrading to GitLab 16.3. + +For more information, see [issue 422938](https://gitlab.com/gitlab-org/gitlab/-/issues/422938). |