diff options
| author | Blair Lunceford <blunceford@gitlab.com> | 2019-07-19 06:25:41 +0000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-07-19 06:25:41 +0000 |
| commit | 4b7277d90e0ca8ce59754531edc8861714294aea (patch) | |
| tree | 8b41161c5dd2f3d51e790443e6d291685f9e2108 | |
| parent | ab105df6090e3a8c504b42806cde1aec9f2ce623 (diff) | |
| download | gitlab-ce-4b7277d90e0ca8ce59754531edc8861714294aea.tar.gz | |
Added new ES rake task and troubleshooting step
| -rw-r--r-- | doc/integration/elasticsearch.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/integration/elasticsearch.md b/doc/integration/elasticsearch.md index 20caac4cb74..626bd259ed6 100644 --- a/doc/integration/elasticsearch.md +++ b/doc/integration/elasticsearch.md @@ -354,6 +354,8 @@ There are several rake tasks available to you via the command line: - Does the same thing as `sudo gitlab-rake gitlab:elastic:create_empty_index` - [sudo gitlab-rake gitlab:elastic:index_snippets](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/ee/lib/tasks/gitlab/elastic.rake) - Performs an Elasticsearch import that indexes the snippets data. +- [sudo gitlab-rake gitlab:elastic:projects_not_indexed](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/ee/lib/tasks/gitlab/elastic.rake) + - Displays which projects are not indexed. ### Environment Variables @@ -469,6 +471,10 @@ Here are some common pitfalls and how to overcome them: The more data present in your GitLab instance, the longer the indexing process takes. +- **There are some projects that weren't indexed, but we don't know which ones** + + You can run `sudo gitlab-rake gitlab:elastic:projects_not_indexed` to display projects that aren't indexed. + - **No new data is added to the Elasticsearch index when I push code** When performing the initial indexing of blobs, we lock all projects until the project finishes indexing. It could |