Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kibana in Chrome doesn't degrade gracefully when there is an issue with returned data #14134

Closed
digitalrinaldo opened this issue Sep 22, 2017 · 3 comments

Comments

@digitalrinaldo
Copy link

Bug

Elasticsearch version (bin/elasticsearch --version):

Version: 5.6.0, Build: 781a835/2017-09-07T03:09:58.087Z, JVM: 1.8.0_144

Plugins installed: []

None

JVM version (java -version):

java version "1.8.0_144"

OS version (uname -a if on a Unix-like system):

4.4.0-1013-aws #22-Ubuntu SMP

Description of the problem including expected versus actual behavior:

Kibana/Chrome has issues when large datasets are returned.

Steps to reproduce:

Perform a query using Kibana in chrome that returns a large amount of data. A 38Mb return is causing the issue today for me. However I have seen this problem over and over.

Do a date historgram in seconds on 180K records and chrome crashes. Was this a silly thing for the user to do yes.

Provide logs (if relevant):

There are no logs, the browser says snap something went wrong every time

@Bargs
Copy link
Contributor

Bargs commented Sep 22, 2017

Can you provide specific examples of scenarios where Kibana crashes? This likely needs to be split into multiple tickets. For instance, we already have a similar ticket for the Discover app specifically. But it sounds like there are other scenarios where you're running into trouble as well.

@rashmivkulkarni
Copy link
Contributor

@Bargs - wdyt of this ticket - can we close it as we are tracking it #11457

@Bargs
Copy link
Contributor

Bargs commented Aug 16, 2018

We never got any feedback so I think it's safe to close, we can reopen if need be.

@Bargs Bargs closed this as completed Aug 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants