You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know through which change (OS update Debian 9 -> Debian 11, Java 8 to Java 11, ElasticSearch 5.6.x to 7.10.x but I think the ElasticSearch is the trigger) the following issue is triggered:
if you run an indexing all process a lot more requests is send to the ElasticSearch service then before. Before I did make this update and had an indexing all running only 20 to 40 requests per second are send to the ElasticSearch service. After this update 1.600 requests per second are send to the ElasticSearch service! This is lot more then before and as we use an application proxy in front of the ElasticSearch service we had a lot more log entries than before. Big parts of the 1.600 requests per second are request to retrieve the current state of the indexed data. I don't know why this is necessary to retrieve this information so many times per second.
The text was updated successfully, but these errors were encountered:
I don't know through which change (OS update Debian 9 -> Debian 11, Java 8 to Java 11, ElasticSearch 5.6.x to 7.10.x but I think the ElasticSearch is the trigger) the following issue is triggered:
if you run an indexing all process a lot more requests is send to the ElasticSearch service then before. Before I did make this update and had an indexing all running only 20 to 40 requests per second are send to the ElasticSearch service. After this update 1.600 requests per second are send to the ElasticSearch service! This is lot more then before and as we use an application proxy in front of the ElasticSearch service we had a lot more log entries than before. Big parts of the 1.600 requests per second are request to retrieve the current state of the indexed data. I don't know why this is necessary to retrieve this information so many times per second.
The text was updated successfully, but these errors were encountered: