-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Performance issues with large alias/index list or mapping #686
Comments
Maybe related to #531 |
It is probably related to the large alias list, we're working to improve that aspect, though I should point out that versions below 0.20.5 are not supported, and 0.20.5 support with be dropped soon. In favor of 0.90 |
@wiibaa: Yeah, seems to be one in the same. @rashidkpc: I mean, fair enough, but it doesn't seem that this would change if I upgraded our cluster to 0.90, so it still stands. :) |
My browser shows that the page locks up while kibana3 is trying to fetch http://my.elasticsearch.host:9200/_all/mapping. So is there an option to close the fetching of all mapping? |
Moved this issue here: #1540 |
@sKabYY +1 |
I'm using the latest Kibana release (v3.0.0pre-milestone5) in conjunction with ElasticSearch 0.19. Any attempts to load the index page results in the browser just locking up for minutes at a time. The page is entirely unusable. I've tried in multiple versions of Chrome, Firefox and Internet Explorer. All the same thing.
I'm convinced this is related to our index count, which is somewhere in the ~2K range, but Kibana 1/2 handled this no problem, so it seems like a pretty big regression that it suddenly can't handle it now, or at least not handle it in a way that doesn't systemically lock up the browser/tab.
Let me know if you need some more information here. I realize it's sort of vague.
The text was updated successfully, but these errors were encountered: