Hi guys, Lately I have been fixing various Elasticsearch flakiness issues in the UTests by: introducing timeouts, countdown latches, force refresh, embedded cluster size decrease ...
These flakiness issues are due to the embedded Elasticsearch not coping well with the jenkins overload. Still, IMHO I believe that having embedded backend for UTests are a lot better than mocks. Even if they are less tolerant to load, I prefer having UTests 100% representative of real backend and add countermeasures to protect against jenkins overload. WDYT ? Etienne
