summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBlair Lunceford <blunceford@gitlab.com>2019-07-12 16:44:50 +0000
committerBlair Lunceford <blunceford@gitlab.com>2019-07-12 16:44:50 +0000
commitcd11ba8c202690c7a89d733aa435650ed10ced1d (patch)
treef8c47e897e496af50d3c71d917448a0f3f5bca83
parentd8e642dece583aa1856a0476edfcc35cdef786ed (diff)
downloadgitlab-ce-docs-add-es-rake-task-blunceford.tar.gz
Added new ES rake task and troubleshooting stepdocs-add-es-rake-task-blunceford
-rw-r--r--doc/integration/elasticsearch.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/integration/elasticsearch.md b/doc/integration/elasticsearch.md
index fff06254da7..79f2d59dd6f 100644
--- a/doc/integration/elasticsearch.md
+++ b/doc/integration/elasticsearch.md
@@ -350,6 +350,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
@@ -465,6 +467,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