# Sample Dashboard Display Issues **URL:** \ **Category:** Elasticsearch\ **Created:** [January 16, 2018, 6:21pm UTC](https://discuss.elastic.co/t/sample-dashboard-display-issues/115771 "2018-01-16T18:21:04Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)\ **Post date:** [January 16, 2018, 6:21pm UTC](https://discuss.elastic.co/t/sample-dashboard-display-issues/115771/1 "2018-01-16T18:21:05Z")
Recently setup an ELK Stack and am having issues after I began feeding it MetricBeat and WinlogBeat data from five servers. When pulling up MetricBeat's sample Host or Overview dashboards I receive one of two types of errors for the modules. rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@5f708265 on QueueResizingEsThreadPoolExecutor[search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 3000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 1.3ms, adjustment amount = 50, QueueResizingEsThreadPoolExecutor[search, queue capacity = 1000, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@10fa6c61[Running, pool size = 7, active threads = 7, queued tasks = 1322, completed tasks = 118090]]] or The aggregations key is missing from the response, check your permissions for this request. Prior to including these five servers, these dashboards loaded fine with just data from the ELK Stack server itself. I've adjusted the max queue capacity from 1000 to 3000 but it hasn't made much of an impact. Below are the server specs, what can I do to resolve this? VMWare VM Server 2012 R2 12GB RAM 4 vCPUs ElasticSearch heap set to 4GB LogStash head set to 2GB Also increased elasticsearch.requestTimeout to 60s in Kibana.yml ---
**Author:** ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)\ **Post date:** [January 19, 2018, 3:02am UTC](https://discuss.elastic.co/t/sample-dashboard-display-issues/115771/2 "2018-01-19T03:02:56Z")
Well, I made a few ElasticSearch configuration modifications, not sure if this is recommended or not but it has made a significant difference. I read the recommended size multiplier was 5 for each core but 25 allowed slightly faster queries, 30 tanked performance. thread\_pool: search: size: 25 queue\_size: 6000 min\_queue\_size: 4000 max\_queue\_size: 6000 target\_response\_time: 1s I also modified Kibana's timeout setting to 60s which helped a lot but there was still the occasional timeout. Increasing it to 120s has resolved timeouts, although that is a LONG time to wait. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 16, 2018, 3:03am UTC](https://discuss.elastic.co/t/sample-dashboard-display-issues/115771/3 "2018-02-16T03:03:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.