kazusa
/
skywalking
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update backend-storage.md (#3222) 

* Update backend-storage.md

* Update backend-storage.md

* Update ES-Server-FAQ.md
This commit is contained in:
吴晟 Wu Sheng 2019-08-06 21:19:00 +08:00 committed by GitHub
parent 1ae04cf2bb
commit eff9faa8c9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 15 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/en/FAQ/ES-Server-FAQ.md
View File

@ -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.

8
docs/en/setup/backend/backend-storage.md
View File

@ -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.