diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-12 00:10:33 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-12 00:10:33 +0300 |
| commit | 63fd08e6b429cd3af81cf63dfc0e5fc853d04086 (patch) | |
| tree | 89f4a922331fb3162ee6e4e839196d41ac96e026 /doc/development/elasticsearch.md | |
| parent | b54cbe2c737b3672737bb7cd1919a030cd75484c (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/elasticsearch.md')
| -rw-r--r-- | doc/development/elasticsearch.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/elasticsearch.md b/doc/development/elasticsearch.md index bc958a27c90..4b87f1c28f1 100644 --- a/doc/development/elasticsearch.md +++ b/doc/development/elasticsearch.md @@ -135,10 +135,10 @@ This is not applicable yet as multiple indices functionality is not fully implem Currently GitLab can only handle a single version of setting. Any setting/schema changes would require reindexing everything from scratch. Since reindexing can take a long time, this can cause search functionality downtime. To avoid downtime, GitLab is working to support multiple indices that -can function at the same time. Whenever the schema changes, the admin +can function at the same time. Whenever the schema changes, the administrator will be able to create a new index and reindex to it, while searches continue to go to the older, stable index. Any data updates will be -forwarded to both indices. Once the new index is ready, an admin can +forwarded to both indices. Once the new index is ready, an administrator can mark it active, which will direct all searches to it, and remove the old index. |