diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-25 06:07:58 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-25 06:07:58 +0000 |
| commit | 9c83aadd2604e7e6cb1f84683f951e6b12872618 (patch) | |
| tree | c0a14c87378e832e87580be382e1c8ccea188b71 /doc/development/elasticsearch.md | |
| parent | 23bc19cb73aad969c9636b8b935111645e809e54 (diff) | |
| download | gitlab-ce-9c83aadd2604e7e6cb1f84683f951e6b12872618.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/elasticsearch.md')
| -rw-r--r-- | doc/development/elasticsearch.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/development/elasticsearch.md b/doc/development/elasticsearch.md index 16a86c06317..20f9fb95440 100644 --- a/doc/development/elasticsearch.md +++ b/doc/development/elasticsearch.md @@ -184,7 +184,7 @@ If the current version is `v12p1`, and we need to create a new version for `v12p You might get an error such as -``` +```plaintext [2018-10-31T15:54:19,762][WARN ][o.e.c.r.a.DiskThresholdMonitor] [pval5Ct] flood stage disk watermark [95%] exceeded on [pval5Ct7SieH90t5MykM5w][pval5Ct][/usr/local/var/lib/elasticsearch/nodes/0] free: 56.2gb[3%], @@ -195,20 +195,20 @@ This is because you've exceeded the disk space threshold - it thinks you don't h In addition, the `read_only_allow_delete` setting will be set to `true`. It will block indexing, `forcemerge`, etc -``` +```shell curl "http://localhost:9200/gitlab-development/_settings?pretty" ``` Add this to your `elasticsearch.yml` file: -``` +```yaml # turn off the disk allocator cluster.routing.allocation.disk.threshold_enabled: false ``` _or_ -``` +```yaml # set your own limits cluster.routing.allocation.disk.threshold_enabled: true cluster.routing.allocation.disk.watermark.flood_stage: 5gb # ES 6.x only |