Bug #3674
Updated by François ARMAND about 11 years ago
After upgrading rudder-server-root from 2.5 to 2.6 now and then searching is not working within the webapp. The connection times out and a popup says "The server cannot be contacted at this time". I had this issue before and we managed to solve it with help from Nicolas Charles. We emptied the database and Rudder was fast again. Since then the problem occured again several times. The webapp is not responsive and I can only search for certain groups (the small ones). Please let's find a definitive solution. Do you recommend me to reinstall Rudder from scratch?
Summary of solution: we need two indexes, 1/ one on RudderSysEvent by execution timestamps, and 2/ one on RudderSysEvent by (execution timestamps and by node)
With only 1/ (and not 2/), we get behaviour described here.
With only 2/ (and not 1/), we get #3926.
<pre>
(1) CREATE INDEX executionTimeStamp_idx on RudderSysEvents (executionTimeStamp);
(2) CREATE INDEX composite_node_execution_idx on RudderSysEvents (nodeId, executionTimeStamp);
</pre>