I just upgraded our existing ES 2.4 cluster to ES 5.2 with following steps:
- Take snapshot of all indices on ES 2.4 cluster
- Remove the ES 2.4 cluster
- Create new ES 5.2 cluster with same hardware configurations
- Restore the last taken snapshot to new created cluster
- Run load test
I found that the query performance on ES 5.2 is much worse then on old ES 2.4 cluster.
On old ES 2.4, the average response time is around 50 ms, now it is 240 ms.
Is this a known perf issue?
We've seen similar degradation. Here the major slowdown was caused by parent-child relationships (defined in the mapping, but not used). Once we rebuilt the indexes without PC, average response times returned to the same interval like in 2.4, but still there are high peaks, which weren't in 2.4.
What is your mapping?
Our index mapping is around 2000 lines, so not possible post here. Can I send the mapping and query DSL to your email?
And is it possible that the worse perf is due to migrating old 2.4 indices to 5.2? Can re-build the indices from scratch help resolve the issue?
Also, is there any ES 5.2 specific perf tuning strategy?
Here you go:
- Since the index was created by restoring the old ES 2.4 snapshot, you can see the "string" instead of "text" in mapping.
- For some fields like Title, Description, we have multiple language specific fields to better support multi-lingual query, like Title_english, Title_german, etc.
- We have nested fields to be used in nested function_score with groovy script_score:
"QueryClicks.Term.lowercaseraw": "elasticsearch 5.2"
More details, please refer to gist.
Does anyone encounter similar obvious query performance degradation after migrated to ES 5.2?
Could you also share the output of the profile API on that particular query? Ideally both with 2.4 and 5.2 so that we can compare.
For the record, there are sme known regressions between 1.x and 2.x but it is the first time I hear of a regression between 2.x and 5.x.
After investigation, the degradation might not be due to 5.2 migration. I am still investigating the root cause, and will get back to you with details.
Thanks your help!
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.