diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-06-29 21:08:57 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-06-29 21:08:57 +0300 |
| commit | aa99514d5c37e08c0fa49d03212ccdc943b8d31e (patch) | |
| tree | c67201d92846b800995fc771c54760d0bf9ce0ae /doc/development/elasticsearch.md | |
| parent | 3aaaf9cd8ecda9552407ffd59e52403696133bab (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/elasticsearch.md')
| -rw-r--r-- | doc/development/elasticsearch.md | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/development/elasticsearch.md b/doc/development/elasticsearch.md index 9f941ad215c..c63e0164e43 100644 --- a/doc/development/elasticsearch.md +++ b/doc/development/elasticsearch.md @@ -218,6 +218,16 @@ be used both locally in development and on any deployed GitLab instance to diagnose poor search performance. This will show the exact queries being made, which is useful to diagnose why a search might be slow. +### Correlation ID and X-Opaque-Id + +Our [correlation +ID](./distributed_tracing.md#developer-guidelines-for-working-with-correlation-ids) +is forwarded by all requests from Rails to Elasticsearch as the +[`X-Opaque-Id`](https://www.elastic.co/guide/en/elasticsearch/reference/current/tasks.html#_identifying_running_tasks) +header which allows us to track any +[tasks](https://www.elastic.co/guide/en/elasticsearch/reference/current/tasks.html) +in the cluster back the request in GitLab. + ## Troubleshooting ### Getting `flood stage disk watermark [95%] exceeded` |