It is an index where data is continuously flowing in. As a result, merges continue to occur, the query cache goes down, and as a result, I/O increases again. What should I do?
below is 1 hour
below is 3 hour
Is it causing issues? What are you seeing as the problem?
@warkolm
The cause is the index that keeps coming in. So it's merged, and the cache goes down because of the merge. Is there any solution?
No, that's typical behaviour for Elasticsearch and it's not something that needs solving.
You're right, this is a common thing in ES, but I was wondering if there was a way to tune it...but it's not.
Could it be better to use "index.store.preload": ["nvd", "dvd"] ?
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.