Reputation: 1270
Question: I create one index with one shard per day on Elasticsearch. When I perform queries against several days worth of these indices, it is very slow. Would anyone that has implemented a similar architecture give some guidance on what could be changed to make the queries more efficient?
Description of the system:
The machines on the cluster are described below. The high IO ones are used in the HOT phase. The high storage are used in the warm and cold phases. The data is replicated in two regions as shown in the picture.
Description of the problem:
When I do a query over these indexes, the query is very slow. To illustrate that, I performed a query for a single _id. It takes more than 40 seconds. The image below is the the kibana output of that query.
It seems for me that ES does not perform the query of each index in parallel. Since when I go to the profiler, the total time it takes seem to be the sum of time times for each of the indices. Below there is the image reflecting the profiler result while also querying for the _id
also posted on the ES discussion forum: https://discuss.elastic.co/t/elasticsearch-query-over-multiple-indexes-very-slow/216520
Upvotes: 2
Views: 2466
Reputation: 1270
For those who might have the same issue, I will post my solution.
My problem was the computers I was using to run ES. The high storage showed to be massively slower!
I changed the kind of deployment to use only high IO ones and didn't change anything else and it runs smoothly now.
Thanks @ibexit for the helpful feedback
Upvotes: 1