diff options
Diffstat (limited to 'doc/integration/elasticsearch.md')
| -rw-r--r-- | doc/integration/elasticsearch.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/integration/elasticsearch.md b/doc/integration/elasticsearch.md index d4ec30e4938..60d6274cfce 100644 --- a/doc/integration/elasticsearch.md +++ b/doc/integration/elasticsearch.md @@ -426,6 +426,15 @@ There are several rake tasks available to you via the command line: - Performs an Elasticsearch import that indexes the snippets data. - [`sudo gitlab-rake gitlab:elastic:projects_not_indexed`](https://gitlab.com/gitlab-org/gitlab/blob/master/ee/lib/tasks/gitlab/elastic.rake) - Displays which projects are not indexed. +- [`sudo gitlab-rake gitlab:elastic:reindex_to_another_cluster[<SOURCE_CLUSTER_URL>,<DESTINATION_CLUSTER_URL>]`](https://gitlab.com/gitlab-org/gitlab/blob/master/ee/lib/tasks/gitlab/elastic.rake) + - Creates a new index in the destination cluster and triggers a [reindex from + remote](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html#reindex-from-remote) + such that the index is fully copied from the source index. This can be + useful when you wish to perform a migration to a new cluster as this + reindexing should be quicker than reindexing via GitLab. Note that remote + reindex requires your source cluster to be whitelisted in your destination + cluster in Elasticsearch settings as per [the + documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html#reindex-from-remote). ### Environment Variables |