Open aerofeev2k opened 2 years ago
Btw, with some unpredictability of the Suggester activity that I'm seeing e.g. here and in the other report where it makes two passes over same project, can Suggester rebuilds be driven completely manually? I know that I can use REST to kick it off, but is there an option to prevent it from making automatic decisions about when to rescan/reload/rebuild?
I mean, if I'm scheduling rebuilds of the main indices manually and at the time when I think it's right for my workflow, it only makes sense for me to have some sort of similarly manual control over when Suggesters uses those indices to rebuild its own DB.
Currently not possible. A tunable would have to be added to avoid all the suggester rebuild() calls.
I've noticed that pulling webapp config and immediately pushing it back triggers Suggester, which in turn brings CPU utilization up to 2000% (I do have rebuildThreadPoolSizeInNcpuPercent set to 10, and there are 40 CPU cores).
The strange thing is that the main indices have not been updated since the last time Suggester has run. I thought that Suggester had these version.txt files with the last seen index generation commit number, so it could've used that as a hint that no rescanning is necessary?
While the Suggester's spinning, I see four threads sitting in about this stack:
I've noticed this because after one such configuration update Tomcat became complete unresponsive, even running out of 8GB of memory: