Live reload fires new request without checking if there is an existing one #2799
The live reload should wait for a response before executing another search request to avoid overloading the server and Elasticsearch cluster.
The live reload fires new search requests against the server according to the live reload interval even if a previous request didn't return yet. (i.e. caused by an overloaded Elasticsearch cluster or a high latency network connection to the Graylog server)
The following screenshot shows an example of this behavior.
Steps to Reproduce (for bugs)
The text was updated successfully, but these errors were encountered: