From eff9faa8c9f1a7f52874afd567ff9d71b5cdb208 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=90=B4=E6=99=9F=20Wu=20Sheng?= Date: Tue, 6 Aug 2019 21:19:00 +0800 Subject: [PATCH] Update backend-storage.md (#3222) * Update backend-storage.md * Update backend-storage.md * Update ES-Server-FAQ.md --- docs/en/FAQ/ES-Server-FAQ.md | 12 +++++++++--- docs/en/setup/backend/backend-storage.md | 8 ++++++-- 2 files changed, 15 insertions(+), 5 deletions(-) diff --git a/docs/en/FAQ/ES-Server-FAQ.md b/docs/en/FAQ/ES-Server-FAQ.md index 938991695..0b2d61365 100644 --- a/docs/en/FAQ/ES-Server-FAQ.md +++ b/docs/en/FAQ/ES-Server-FAQ.md @@ -1,5 +1,9 @@ # ElasticSearch -Some new user may face the following error in ElasticSearch storage. ERROR CODE 429. Or ElasticSearch performance is not as good as expected. +Some new users may face +* ElasticSearch performance is not as good as expected. Such as, can't have latest data after a while. + +Or +* ERROR CODE 429. ``` Suppressed: org.elasticsearch.client.ResponseException: method [POST], host [http://127.0.0.1:9200], URI [/service_instance_inventory/type/6_tcc-app-gateway-77b98ff6ff-crblx.cards_0_0/_update?refresh=true&timeout=1m], status line [HTTP/1.1 429 Too Many Requests] {"error":{"root_cause":[{"type":"remote_transport_exception","reason":"[elasticsearch-0][10.16.9.130:9300][indices:data/write/update[s]]"}],"type":"es_rejected_execution_exception","reason":"rejected execution of org.elasticsearch.transport.TransportService$7@19a5cf02 on EsThreadPoolExecutor[name = elasticsearch-0/write, queue capacity = 200, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@389297ad[Running, pool size = 2, active threads = 2, queued tasks = 200, completed tasks = 147611]]"},"status":429} @@ -12,9 +16,11 @@ Some new user may face the following error in ElasticSearch storage. ERROR CODE You could add following config to `elasticsearch.yml`, set the value based on your env. ```yml # In tracing scenario, consider to set more than this at least. -thread_pool.index.queue_size: 500 -thread_pool.write.queue_size: 500 +thread_pool.index.queue_size: 1000 +thread_pool.write.queue_size: 1000 # When you face query error at trace page, remember to check this. index.max_result_window: 1000000 ``` + +Read ElasticSearch official documents to get more information. diff --git a/docs/en/setup/backend/backend-storage.md b/docs/en/setup/backend/backend-storage.md index da0a78c07..6fd8339a2 100644 --- a/docs/en/setup/backend/backend-storage.md +++ b/docs/en/setup/backend/backend-storage.md @@ -56,6 +56,12 @@ storage: ### Data TTL TTL in ElasticSearch overrides the settings of core, read [ElasticSearch section in TTL document](ttl.md#elasticsearch-6-storage-ttl) +### Elasticearch server settings +Read the [ElasticSearch storage FAQ](../../FAQ/ES-Server-FAQ.md) if you are new to ElasticSearch. +And recommend read more about these configuration from ElasticSearch official document. +This effects the performance of ElasticSearch very much. + + ### ElasticSearch 6 with Zipkin trace extension This implementation shares most of `elasticsearch`, just extend to support zipkin span storage. It has all same configs. @@ -79,8 +85,6 @@ storage: concurrentRequests: ${SW_STORAGE_ES_CONCURRENT_REQUESTS:2} # the number of concurrent requests ``` -Read the [ElasticSearch storage FAQ](../../FAQ/ES-Server-FAQ.md) if you are new to ElasticSearch. And recommend read more about these configuration from ElasticSearch official document. This effects the performance of ElasticSearch very much. - ### ElasticSearch 6 with Jaeger trace extension This implementation shares most of `elasticsearch`, just extend to support zipkin span storage. It has all same configs.