You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A cluster that contains indices with large mappings, such as Filebeat or Metricbeat indices, can cause significant slowdown and unresponsiveness in Opensearch Dashboards.
To Reproduce
Set up a 2-node development cluster as per the docs here:
Note that I updated the heap size to 5g for each node and I'm running this on a c8.m16 VM.
Export the index template for filebeat 7.12.1:
docker run docker.elastic.co/beats/filebeat-oss:7.12.1 filebeat export template --noilm > template.json
Run the following python script that creates the index template and 500 indices based on this template (requires elasticsearch==7.12.1 to be installed):
Press Ctrl-<enter> around 50 times consecutively to run the requests in quick succession.
Try opening Discover in a new tab
If things still seem ok, try doing step 4 again.
Expected behavior
I expect those _cat/health requests to return very quickly and not take tens of seconds and sometimes even time out. Note that if you comment out the template loading step in the script so that the indices are created with no mappings, then the requests do return instantly. Also, even if the template is loaded, executing a python script that runs _cat/health many times in succession doesn't experience the same slowdown.
I expect the Discover app to load and not just hang indefinitely.
Note that I can't reproduce this behaviour in 2.10.0. It's slower than I would like, but the requests don't take as long and it doesn't become unresponsive.
OpenSearch Version
2.16.0
Dashboards Version
2.16.0
Plugins
Using the stock opensearchproject/opensearch-dashboards:2.16.0 image.
Screenshots
N/A
Host/Environment (please complete the following information):
Windows 10
Chrome 128.0.6613.120
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Describe the bug
A cluster that contains indices with large mappings, such as Filebeat or Metricbeat indices, can cause significant slowdown and unresponsiveness in Opensearch Dashboards.
To Reproduce
https://opensearch.org/docs/latest/install-and-configure/install-opensearch/docker/#sample-docker-compose-file-for-development
Note that I updated the heap size to 5g for each node and I'm running this on a c8.m16 VM.
elasticsearch==7.12.1
to be installed):Press Ctrl-<enter> around 50 times consecutively to run the requests in quick succession.
If things still seem ok, try doing step 4 again.
Expected behavior
_cat/health
requests to return very quickly and not take tens of seconds and sometimes even time out. Note that if you comment out the template loading step in the script so that the indices are created with no mappings, then the requests do return instantly. Also, even if the template is loaded, executing a python script that runs_cat/health
many times in succession doesn't experience the same slowdown.OpenSearch Version
2.16.0
Dashboards Version
2.16.0
Plugins
Using the stock
opensearchproject/opensearch-dashboards:2.16.0
image.Screenshots
N/A
Host/Environment (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: