-
Bug
-
Resolution: Done
-
Major
-
None
-
1
-
False
-
False
-
NEW
-
NEW
-
-
-
Logging (Explore) - Sprint 198
While under the es cluster is under load, it is possible for the cron jobs to fail due to receiving a http 500 response from elasticsearch.
To recreate this locally I did the following:
1) Spin up a 3 node es cluster (I used 1G memory and 500m cpu)
2) Configure cronjobs to run every minute and rollover after 1 minute and delete after 5
3) Put a small load on the server (I created a script that would create x number of indices with a small message) and could usually see crons error due to a 500 while it was creating 800 indices.
4) Watch for cronjobs to error out (and confirm it was due to a 500)