# Queries failing on Marvel Dashboard

**URL:** <https://discuss.elastic.co/t/queries-failing-on-marvel-dashboard/2267>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [June 10, 2015, 2:20am UTC](https://discuss.elastic.co/t/queries-failing-on-marvel-dashboard/2267 "2015-06-10T02:20:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bsarkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bsarkar/32/42967_2.png) [@bsarkar](https://discuss.elastic.co/u/bsarkar)\
**Post date:** [June 10, 2015, 2:20am UTC](https://discuss.elastic.co/t/queries-failing-on-marvel-dashboard/2267/1 "2015-06-10T02:20:08Z")

</div>

Elasticsearch Version - 1.3.4  
Marvel Version - 1.2.1

We have separate clusters for Marvel indices and indices containing actual data. Recently we shutdown all Marvel nodes, deleted the data folder on each of those nodes and restarted Elasticsearch service on all Marvel nodes. When we open the Marvel dashboard, we could see proper plots for Document Count, Search Request Rate and Indexing Request Rate. But there was no plot in Indices and Nodes sections below. Instead it keeps on showing the following error message:

```
Oops! SearchParseException[[.marvel-2015.06.10][0]: query[ConstantScore(BooleanFilter(+*:* +cache(_type:node_stats) +cache(@timestamp:[1433901960000 TO 1433902620000])))],from[-1],size[10]: Parse Failure [Failed to parse source [{"size":10,"query":{"filtered":{"query":{"match_all":{}},"filter":{"bool":{"must":[{"match_all":{}},{"term":{"_type":"node_stats"}},{"range":{"@timestamp":{"from":"now-10m/m","to":"now/m"}}}]}}}},"facets":{"timestamp":{"terms_stats":{"key_field":"node.ip_port.raw","value_field":"@timestamp","order":"term","size":2000}},"master_nodes":{"terms":{"field":"node.ip_port.raw","size":2000},"facet_filter":{"term":{"node.master":"true"}}},"os.cpu.usage":{"terms_stats":{"key_field":"node.ip_port.raw","value_field":"os.cpu.usage","order":"term","size":2000}},"os.load_average.1m":{"terms_stats":{"key_field":"node.ip_port.raw","value_field":"os.load_average.1m","order":"term","size":2000}},"jvm.mem.heap_used_percent":{"terms_stats":{"key_field":"node.ip_port.raw","value_field":"jvm.mem.heap_used_percent","order":"term","size":2000}},"fs.total.available_in_bytes":{"terms_stats":{"key_field":"node.ip_port.raw","value_field":"fs.total.available_in_bytes","order":"term","size":2000}},"fs.total.disk_io_op":{"terms_stats":{"key_field":"node.ip_port.raw","value_field":"fs.total.disk_io_op","order":"term","size":2000}}}}]]]

```

It has been around 12 hours now and the message has not gone away. Any idea what could be wrong here?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:48pm UTC](https://discuss.elastic.co/t/queries-failing-on-marvel-dashboard/2267/2 "2017-07-06T13:48:01Z")

</div>