Our production ELK stack suddenly stopped being able to create indexes for exceptions recently.
We're using the NEST C# library in the application, and events (purchases, site activity) are still able to create indexes, which is done with identical code (minus the index name and object being passed).
Elasticsearch logs say: http://pastebin.com/1XA2Kavb
I can't recreate the issue in my dev environment (logs everything just fine), which tells me the issue isn't in the application code (which I'll paste below anyway). I recently tried putting a template, which I believe is when the issue started, and attempts to clear it didn't seem to fix the issue. Ideally I'd be able to fix this without a restart, some googling tells me that may have to happen. Any ideas? I'm happy to provide any other information that would be helpful.
Here's the c# snippet:
var index = client.Index(elkception, i => i .Index("exceptions-" + DateTime.Now.ToString("yyyy-MM-dd")) .Type(elkception.TypeOfException) .Refresh() .Ttl("1m") );