elasticsearch_max_time_per_index configuratoin leads to ArithmeticException division by zero #836
I'm using the latest graylog2 v0.93-3 version with elasticinbox 1.4.x . i've added the following parameter in the graylog2.conf :
to keep the index 30d persisted. After restarting the graylog2-server service, I'm seeing the following message in the server.log
changing the parameter to 31d, 720h, 721h and even 24h results in the same error.
Configuring the parameter with 5h, like:
and restarting graylog2-server, it works well.
I'm running on an ubuntu 12.04 LTS
The text was updated successfully, but these errors were encountered:
the determined anchor is still not ideal for non-scalar periods (i.e. period which mix field types like 30d == 4w 2d), but it doesn't crash anymore fixes #836