zipkin: Elasticsearch http slow on getting span names when there's a lot of data
from @dragontree101
because of we have lots of data, service name and span name all time out, i remember store data in cassandra, have table only store service_name and span_name, but store in es, service_name and span_name get by es, so time is very long.

and chrome console have

i found i set SELF_TRACING_ENABLED=“true” in environment

and yestoday’s es index is
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open zipkin-2016-12-29 2_uXTThATbyoJ7khnXbo4g 5 1 609199726 0 140gb 70gb
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 32 (16 by maintainers)
Commits related to this issue
- Don't sort span names in elasticsearch While probably not a big contributor to performance, we don't need to sort span names in elasticsearch as we already copy out into a sorted list. See #1462 — committed to openzipkin/zipkin by deleted user 8 years ago
- Don't sort span names in elasticsearch (#1463) While probably not a big contributor to performance, we don't need to sort span names in elasticsearch as we already copy out into a sorted list. S... — committed to openzipkin/zipkin by adriancole 7 years ago
- Limits names lookback in Elasticsearch This reuses `QUERY_LOOKBACK` to limit names queries (service and span names) from searching all indexes. This is particularly important for high-volume sites (e... — committed to openzipkin/zipkin by deleted user 7 years ago
- Limits names lookback in Elasticsearch (#1538) This reuses `QUERY_LOOKBACK` to limit names queries (service and span names) from searching all indexes. This is particularly important for high-volum... — committed to openzipkin/zipkin by adriancole 7 years ago
Thanks. Will look into this and let you know.