cerebro
cerebro copied to clipboard
lmenezes
REST autocomplete very slow when having a large number of indexes/aliases
Hello,
I am noticing a case where the autocomplete section of the REST page (where the index / url is entered) it is very slow when accessing a cluster with hundreds of indexes (and even more aliases). It can take several minutes to load and makes the page hard to use.
It would be nice if this were faster, or even disabling autocomplete if the number of results is too large. Thanks!
I have also thousand of indices, and is the interface is not responding anymore. it consumes all the cpu usage where I installed the cerberus.
This happens also for our setup. We have 2k+ indices and 10k+ aliases (each index has in average 5 aliases) and after updating from 0.8.5 to 0.9.2, REST interface is freezing, when we try to write something in path input. LE: It freezes also when we try to write some query parameters (e.g: wait_for_completion).
@pp88888 @cantipop @orinciog Which browser/version are you using? Did you notice this effect from one version to another? I assume you have no issues with other parts of the app? Also, I imagine there is not a problem fetching the data?(when first opening the REST screen, there is call made to /rest to fetch this info)
@lmenezes I have tested with 2 browsers:
Firefox 84.0.1 Chrome Version 87.0.4280.88 (Official Build) (x86_64)
both in OSX 10.15.7. I see the same behavior, the autocomplete become unresponsive. Other parts of the app are fine. I reviewed in network tools and I see the JSON response for the rest endpoint being served pretty quickly. (it is has 6K+ indices on it).
@lmenezes
I'm using two browsers: Firefox 84.0 and Chrome Version 87.0.4280.88 (Official Build) (64-bit) on Ubuntu 18.04.
Both are having same behavior in rest app.
/rest route is served in 600ms with 600KB received. All other parts are ok, for example the biggest timing route is /overview with 4.4MB received in 6 seconds.
I observed this behavior when I updated cerebro docker from 0.8.5 to 0.9.2.
Did you try v0.9.3? We added a fix for #467. Basically if you have many closed indices the performance gets worse.
@moliware Sure, I will test 0.9.3, but I don't have closed indices. All 2K+ indices are open.
Hello @moliware I'm running 0.9.4 and still experience this -- fwiw our indices are open as well.
I noticed that the issue is not the REST call, but in the JS responding to the JSON payload. @moliware