Leap Day Issues?


Just curious if anyone else is experiencing leap day issues. I'm creating a daily index with Logstash, so today's index looks something like logstash-{custom_name}-2016.02.29 with "Index contains time-based events" enabled, and Kibana started throwing an error today:

Courier Fetch: [unsupported_operation_exception] custom format isn't supported

Version: 4.3.0
Build: 9369
Error: [unsupported_operation_exception] custom format isn't supported
    at respond (http://<hostname_removed>:5601/bundles/kibana.bundle.js:76160:16)
    at checkRespForFailure (http://<hostname_removed>:5601/bundles/kibana.bundle.js:76123:8)
    at http://<hostname_removed>:5601/bundles/kibana.bundle.js:74741:8
    at processQueue (http://<hostname_removed>:5601/bundles/commons.bundle.js:42339:29)
    at http://<hostname_removed>:5601/bundles/commons.bundle.js:42355:28
    at Scope.$eval (http://<hostname_removed>:5601/bundles/commons.bundle.js:43583:29)
    at Scope.$digest (http://<hostname_removed>:5601/bundles/commons.bundle.js:43394:32)
    at Scope.$apply (http://<hostname_removed>:5601/bundles/commons.bundle.js:43691:25)
    at done (http://<hostname_removed>:5601/bundles/commons.bundle.js:38140:48)
    at completeRequest (http://<hostname_removed>:5601/bundles/commons.bundle.js:38338:8)

I'm going to try reindexing data using a different name to see if that helps. Just wanted to see if anyone else had the same issue and if there is any resolution.


Discovered the issue, though I'm not sure on the root cause yet. Somehow Logstash created an index with the wrong format (logstash-4568844.09.02) which threw off Kibana.

(丽娜季) #3

Then how can we resolve it?

Is logstash-4568844.09.02 a file?

I encounter the issue almost every time when I import new data.


In my case, this was a data issue. On leap day this year, one of my data sources produced an invalid date which caused Logstash to create an index that didn't match the date pattern I configured in Kibana. To get around it, I simply deleted the invalid index. Of course, you'll lose whatever data you had in that index, but in my case I was able to live with it since it was only one record of insignificant data that caused this to happen.

(system) #5