Closed jamiesmith closed 4 years ago
Pinging @elastic/kibana-canvas
Thanks for filing @jamiesmith. @w33ble @clintandrewhall this environment might be a good way to reproduce intermittent performance issues on our cloud environment.
Thanks @alexfrancoeur ... this is really detailed and helpful... you're awesome, @jamiesmith !!
Closing this as all of these issues should be solved in the 7.x series, please re-open if not.
Kibana version: 6.5.0
Elasticsearch version: 6.5.0
Server OS version: ECE
There isn't much data on these clusters - We are set up to have 32gb RAM for Elasticsearch, and 4gb RAM for the Kibana instance.
Browser version: Chrome Version 71.0.3578.98 (Official Build) (64-bit) and Safari Version 12.0.1 (14606.2.104.1.1)
Browser OS version: MacOS 10.14.1
Original install method (e.g. download page, yum, from source, etc.): ECE/6.5.0 stack pack Note that the ECE demo env runs behind an oauth proxy
Describe the bug:
This is really an "across the board" set of things that keep happening with two of our canvas demos in the SA demo environment. General performance issues, errors, 404's, websocket retries, slow/not loading workpads-- even just getting the list of workpads. The issues of things not loading at all is intermittent, but the slowness persists - in the middle of writing this ticket it started working again, then started failing again (failing, meaning it never finished loading the workpad or list of workpads). I have tried several different workpads. Often, just the the "canvas is loading" thing shows up, or it gets stuck on a workpad with the clocks and never finishes loading.
As I was typing this, it started working, then got back into another stall:![image](https://user-images.githubusercontent.com/220994/50775588-8b9f1900-1264-11e9-8b13-833cb9065d98.png)
Steps to reproduce:
Visit the IoT or canvas demos in the SA Demo Env (ping jamie.smith on slack for the address of them if you don't know them)
Expected behavior:
Screenshots (if relevant): This page got stuck in this state (3 minutes, never finished):
with nothing other than the websocket errors and one of these in the console:
canvas.bundle.js:4 GET https://canvas.<redacted>/socket.io/?EIO=3&transport=polling&t=MWewhO4&sid=0i_CNJSnL9yUHxCZAIBo net::ERR_CONNECTION_CLOSED
Errors in browser console (if relevant): We continually get the WebSocket error, which is expected because of the proxy, but I don't know why it keeps trying a websocket when it's not supported.
Various permutations of these errors in chrome:
And some different ones in safari, on a different load:
Provide logs and/or server output (if relevant): If I get access to the ES/Kibana logs for the timeframe (07-jan-2019 @ ~9:10 am EST) I will add them
Any additional context:
Note that this is intermittent. Canvas loads are usually pretty slow, even for small ones (much, much slower than running locally). Some more visibility as to what is going on would be helpful. In this case, the "canvas is loading" was on the screen for a couple of minutes before I finally opened up devtools to see that it was looping
Also pinging @mindbat who does a lot of work with the SA demo env.