I was running the newest version of Kibana, 7.6. I was noticing that during ingestion process, some of my visualizations are taking over 30 seconds. When they take that long it will expose the error:
[esaggs] > Unexpected token u in JSON at position 0
When looking at the network request, it says cancelled. I think that it auto-cancels requests but it seems that the timeout will occur around the 30 second mark.
I have some visualizations for the last 2 days, pretty much monitoring the counts of ingestion per host. I am running a single, dual purpose data/master node, which is likely why kibana requests are taking so long.
Before I start building out and adding more machines to the ES instance, I want to see if this is actually a bug or not. It seems that sometimes when I set the relative conditions to under 3 recent hours, it will display the graphs.
Thoughts or recommendations?
The error message isn't nice and doesn't really help. There is an issue for this which is actively worked on: https://github.com/elastic/kibana/issues/57327
You are completely correct though - the Kibana server is taking longer than 30 seconds to fetch the data from Elasticsearch, this is why it gives up and just shows an error. If your requests sometimes take longer, you can increase the value in your
kibana.yml file by giving
elasticsearch.requestTimeout a value greater than
30000 (the unit is ms). The default is just in place here to prevent super expensive queries submitted by accident to run forever and slowing down your cluster.
That being said, > 30s load time is a lot. Maybe it is possible to tune your server a bit without adding hardware. For guidance around this you can post in the ES forum and I'm sure you will find help.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.