# Kibana Monitoring Nodes - There are no records that match your query **URL:** \ **Category:** Kibana\ **Created:** [July 25, 2018, 7:02pm UTC](https://discuss.elastic.co/t/kibana-monitoring-nodes-there-are-no-records-that-match-your-query/141653 "2018-07-25T19:02:26Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [July 25, 2018, 7:02pm UTC](https://discuss.elastic.co/t/kibana-monitoring-nodes-there-are-no-records-that-match-your-query/141653/1 "2018-07-25T19:02:26Z")
I set search.max\_buckets=10000 because our cluster was breaking at times when we got these messages in the log. After that change, I went to the monitoring screen listing the nodes, it worked for "last 15 minutes" gets: "no records that match" for "last 1 hour" or longer. Version 6.3.1 ---
**Author:** ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)\ **Post date:** [August 6, 2018, 4:52pm UTC](https://discuss.elastic.co/t/kibana-monitoring-nodes-there-are-no-records-that-match-your-query/141653/2 "2018-08-06T16:52:20Z")
Hi @rugenl, Can you open the network tab in the developer tools and find the `cluster` request and paste the entire request/response here? ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [August 6, 2018, 11:32pm UTC](https://discuss.elastic.co/t/kibana-monitoring-nodes-there-are-no-records-that-match-your-query/141653/3 "2018-08-06T23:32:01Z")
Request URL: https://...missouri.edu/api/monitoring/v1/clusters/DWNq4pOHTOuOfdYShnhaig/elasticsearch/nodes Request Method: POST Status Code: 200 OK Remote Address: xxx.xxx.xxx.xxx:443 Referrer Policy: no-referrer-when-downgrade cache-control: no-cache Connection: Keep-Alive content-encoding: gzip content-type: application/json; charset=utf-8 Date: Mon, 06 Aug 2018 23:21:44 GMT kbn-name: kibana kbn-version: 6.3.2 kbn-xpack-sig: b222b911b1ef01c0b10618e8215698f5 Keep-Alive: timeout=5, max=99 Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips Transfer-Encoding: chunked vary: accept-encoding Accept: application/json, text/plain, _/_ Accept-Encoding: gzip, deflate, br Accept-Language: en-US,en;q=0.9 Authorization: Basic bWV0cmljc3RlYW06aGlkZGVuRUxL Connection: keep-alive Content-Length: 81 Content-Type: application/json;charset=UTF-8 Cookie: \_ga=GA1.2.1804478381.1511274427; \_\_utma=262015377.1804478381.1511274427.1525787649.1525787649.1; \_\_utmz=262015377.1525787649.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=(not%20provided) Host: ...missouri.edu kbn-version: 6.3.2 Origin: https://...missouri.edu Referer: https://....missouri.edu/app/monitoring User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.84 Safari/537.36 {"timeRange":{"min":"2018-08-06T22:21:43.608Z","max":"2018-08-06T23:21:43.609Z"}} {"clusterStatus":{"status":"green","indicesCount":110,"documentCount":2663868064,"dataSize":2671062360767,"nodesCount":14,"upTime":292134182,"version":["6.3.2"],"memUsed":77090275992,"memMax":274076008448,"unassignedShards":0,"totalShards":564},"nodes":[] ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [August 7, 2018, 12:16am UTC](https://discuss.elastic.co/t/kibana-monitoring-nodes-there-are-no-records-that-match-your-query/141653/4 "2018-08-07T00:16:47Z")
It gets the max\_buckets error [2018-08-06T19:14:40,613][WARN][r.suppressed] path: /.monitoring-es-2-_%2C.monitoring-es-6-_/\_search, params: {size=10000, ignore\_unavailable=true, index=.monitoring-es-2-_,.monitoring-es-6-_, filter\_path=hits.total,hits.hits.\_source.source\_node,aggregations.nodes.buckets.key,aggregations.nodes.buckets.node\_cgroup\_quota.buckets,aggregations.nodes.buckets.node\_cgroup\_throttled.buckets,aggregations.nodes.buckets.node\_cpu\_utilization.buckets,aggregations.nodes.buckets.node\_load\_average.buckets,aggregations.nodes.buckets.node\_jvm\_mem\_percent.buckets,aggregations.nodes.buckets.node\_free\_space.buckets} org.elasticsearch.action.search.SearchPhaseExecutionException: at org.elasticsearch.action.search.AbstractSearchAsyncAction.onPhaseFailure(AbstractSearchAsyncAction.java:288) [elasticsearch-6.3.2.jar:6.3.2] at org.elasticsearch.action.search.FetchSearchPhase$1.onFailure(FetchSearchPhase.java:91) [elasticsearch-6.3.2.jar:6.3.2] at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.onFailure(ThreadContext.java:710) [elasticsearch-6.3.2.jar:6.3.2] at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:39) [elasticsearch-6.3.2.jar:6.3.2] at org.elasticsearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:41) [elasticsearch-6.3.2.jar:6.3.2] at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-6.3.2.jar:6.3.2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0\_171] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0\_171] at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_171] Caused by: org.elasticsearch.search.aggregations.MultiBucketConsumerService$TooManyBucketsException: Trying to create too many buckets. Must be less than or equal to: [10000] but was [10001]. This limit can be set by changing the [search.max\_buckets] cluster level setting. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 4, 2018, 12:17am UTC](https://discuss.elastic.co/t/kibana-monitoring-nodes-there-are-no-records-that-match-your-query/141653/5 "2018-09-04T00:17:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.