[Engineering] Logstash goofyness from 2016-01-01 through 2016-01-20 (seeking input)

[Antoine Musso]

Le 26/01/2016 19:51, Bryan Davis a écrit :
> The rogue 2015-01-* indices have all been dropped. Restarting the
> Logstash processes seem to have corrected all of their confusion. I'm
> going to write this off to Java + JRuby weirdness for now.
> 
> Bryan

Sounds good, thank you for baby sitting logstash!


-- 
Antoine "hashar" Musso