Kibana Dashboard timing out after 30000ms when opened in new tab of browser

[Darshan_v_Shah (Darshan Shah)]

Hi team,

I am facing as issue where the Kibana dashboard crashes on the browser saying

Version: 6.7.2
Build: 20334
SearchError: Request Timeout after 30000ms
at http://ec2-3-19-110-7.us-east-2.compute.amazonaws.com:5601/bundles/commons.bundle.js:4:383522
at processQueue (http://ec2-3-19-110-7.us-east-2.compute.amazonaws.com:5601/built_assets/dlls/vendors.bundle.dll.js:450:199687)
at http://ec2-3-19-110-7.us-east-2.compute.amazonaws.com:5601/built_assets/dlls/vendors.bundle.dll.js:450:200650
at Scope.$digest (http://ec2-3-19-110-7.us-east-2.compute.amazonaws.com:5601/built_assets/dlls/vendors.bundle.dll.js:450:210412)
at http://ec2-3-19-110-7.us-east-2.compute.amazonaws.com:5601/built_assets/dlls/vendors.bundle.dll.js:450:212944
at completeOutstandingRequest (http://ec2-3-19-110-7.us-east-2.compute.amazonaws.com:5601/built_assets/dlls/vendors.bundle.dll.js:450:64425)
at http://ec2-3-19-110-7.us-east-2.compute.amazonaws.com:5601/built_assets/dlls/vendors.bundle.dll.js:450:67267

It is reproducible if you set the dashboard to auto refresh and start doing your chores on other tabs. You will notice that it should be able to see the same error. Why so ? What are the suggestions for this?

What I understand is that Kibana is keeping a track of my "focus"/"blur"( probably ) to understand if I am looking or not. If I keep looking at the tab, it never fails. Or also if I open it as a separate browser window.

I am not able to completely understand the part where, when I open inspect and check network, i see that during the period when I was not looking, there was no network activity. No requests even. So why the request timeout ?

This is not just on my setup of kibana, I have tried the auto refresh on your kibana too :-
demo.elastic.co/app/kibana#/dashboard/79ffd6e0-faa0-11e6-947f-177f697178b8-ecs
As mentioned previously, just open this and starting working on other tabs and let me know if you face it.

I have attached some screenshots for both.

I also have tried reducing the shards from 1000 to 300. I have a increased the node size from 2Core4GB RAM to 8Core32GB RAM. It did not help.

My chrome

Google Chrome is up to date
Version 75.0.3770.100 (Official Build) (64-bit)

Initial errors:-

End result:-

Also for me :-

Any inputs will be greatly valued.
Thanks,
Darshan

[jen-huang]

Hi, I tried the demo dashboard you linked to and kept it in a background tab for a few minutes and did not get the same thing you experienced. I opened the Network information in a new window for that tab and observed that data calls were still being made while the tab was in the background.

I am not able to completely understand the part where, when I open inspect and check network, i see that during the period when I was not looking, there was no network activity. No requests even. So why the request timeout ?

You need to open network tabe before putting it as a background tab.. It only captures information when it is open. So try that out and see if you see any failing requests being made.

In addition, I'd like to know what your auto-refresh frequency is? (I did the default every 5 seconds) Please also try in a different browser like Firefox, and an incognito Chrome session as well. Thank you.

[Darshan_v_Shah (Darshan Shah)]

Hi,

Thanks for the reply.

The new window method works for me, as I mentioned.

But new tab in the same window is the problem.
I start inspect and confirm few calls being done and then open/move over to other tabs, but in the same window. After few minutes I return and start seeing errors and there is a big gap in the network activity. I see you mention trying with new window. Have you tried this?

Also i have tried this with firefox as well.
But it's the same result. I can definitely give a try to a browser on a different device.

Thanks,
Darshan

[Darshan_v_Shah (Darshan Shah)]

The chrome browser seems to throttle auto-refresh timers of background pages. Disabling it here :

chrome://flags/#expensive-background-timer-throttling

then worked for me.

Thanks