# SearchParseException (marvel) - \[No mapping found for \[@timestamp\] in order to sort on **URL:** \ **Category:** Elasticsearch\ **Created:** [December 14, 2014, 4:22pm UTC](https://discuss.elastic.co/t/searchparseexception-marvel-no-mapping-found-for-timestamp-in-order-to-sort-on/21250 "2014-12-14T16:22:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Eugen\_Paraschiv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eugen_paraschiv/32/919_2.png) [@Eugen\_Paraschiv](https://discuss.elastic.co/u/Eugen_Paraschiv)\ **Post date:** [December 14, 2014, 4:22pm UTC](https://discuss.elastic.co/t/searchparseexception-marvel-no-mapping-found-for-timestamp-in-order-to-sort-on/21250/1 "2014-12-14T16:22:22Z")
Hi, I'm using Elasticsearch 1.4.1 and the latest Marvel (1.2.1). I have Marvel installed on every node of the cluster and generating data into the daily index. When going into Marvel, I get the following exception: Caused by: org.elasticsearch.search.SearchParseException: [.marvel-2014.12. 14][0]: from[-1],size[1]: Parse Failure [No mapping found for [@timestamp] in order to sort on] So - this is referring specifically to the _.marvel-2014.12.14_ index - an index created by Marvel itself, which should thus have the right structure. Am I missing something related to the Marvel setup? Thank you, Eugen. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/71932dba-a12f-4b48-874b-c51fc660dbd2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/71932dba-a12f-4b48-874b-c51fc660dbd2%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Eugen\_Paraschiv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eugen_paraschiv/32/919_2.png) [@Eugen\_Paraschiv](https://discuss.elastic.co/u/Eugen_Paraschiv)\ **Post date:** [December 14, 2014, 7:42pm UTC](https://discuss.elastic.co/t/searchparseexception-marvel-no-mapping-found-for-timestamp-in-order-to-sort-on/21250/2 "2014-12-14T19:42:22Z")
One more detail on this - the Marvel UI also displays the exact query that's failing. Running that query results in a more informative message - probably the root cause of the problem: Caused by: org.elasticsearch.search.facet.FacetPhaseExecutionException: Facet [fs.total.available\_in\_bytes]: failed to find mapping for fs.total. available\_in\_bytes And indeed, the _fs.total.available\_in\_bytes_ isn't available in in the marvel index. Now - the reading is available on _\_nodes/stats_ - so I'm assuming it's a mapping problem from Marvel. But - I removed the old mapping, restarted the entire cluster and basically allowed marvel to re-create the mapping it needs - so that should be correct. Any help is appreciated. Thanks. On Sunday, December 14, 2014 6:22:22 PM UTC+2, Eugen Paraschiv wrote: > Hi, > I'm using Elasticsearch 1.4.1 and the latest Marvel (1.2.1). > I have Marvel installed on every node of the cluster and generating data > into the daily index. > When going into Marvel, I get the following exception: > Caused by: org.elasticsearch.search.SearchParseException: [.marvel-2014.12 > .14][0]: from[-1],size[1]: Parse Failure [No mapping found for [@timestamp > ] in order to sort on] > > So - this is referring specifically to the _.marvel-2014.12.14_ index - > an index created by Marvel itself, which should thus have the right > structure. > Am I missing something related to the Marvel setup? > Thank you, > Eugen. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/e2f43a38-3062-4253-a519-38b3bb3c1c1e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e2f43a38-3062-4253-a519-38b3bb3c1c1e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [December 20, 2014, 8:58am UTC](https://discuss.elastic.co/t/searchparseexception-marvel-no-mapping-found-for-timestamp-in-order-to-sort-on/21250/3 "2014-12-20T08:58:12Z")
I would check your ES installation. This information comes from the Node Stats API, so it is likely missing there as well. Most of the time this is caused by missing the Sigar library or some process permission issue. Cheers, Boaz On Sunday, December 14, 2014 8:42:22 PM UTC+1, Eugen Paraschiv wrote: > One more detail on this - the Marvel UI also displays the exact query > that's failing. Running that query results in a more informative message - > probably the root cause of the problem: > Caused by: org.elasticsearch.search.facet.FacetPhaseExecutionException: > Facet [fs.total.available\_in\_bytes]: failed to find mapping for fs.total. > available\_in\_bytes > And indeed, the _fs.total.available\_in\_bytes_ isn't available in in the > marvel index. > Now - the reading is available on _\_nodes/stats_ - so I'm assuming it's a > mapping problem from Marvel. > But - I removed the old mapping, restarted the entire cluster and > basically allowed marvel to re-create the mapping it needs - so that should > be correct. > Any help is appreciated. > Thanks. > > On Sunday, December 14, 2014 6:22:22 PM UTC+2, Eugen Paraschiv wrote: > > > Hi, > > I'm using Elasticsearch 1.4.1 and the latest Marvel (1.2.1). > > I have Marvel installed on every node of the cluster and generating data > > into the daily index. > > When going into Marvel, I get the following exception: > > Caused by: org.elasticsearch.search.SearchParseException: [.marvel- > > 2014.12.14][0]: from[-1],size[1]: Parse Failure [No mapping found for [ > > @timestamp] in order to sort on] > > > > So - this is referring specifically to the _.marvel-2014.12.14_ index - > > an index created by Marvel itself, which should thus have the right > > structure. > > Am I missing something related to the Marvel setup? > > Thank you, > > Eugen. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/81834d9b-546c-4ef9-80d9-a53ba4dd9bc2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/81834d9b-546c-4ef9-80d9-a53ba4dd9bc2%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Eugen\_Paraschiv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eugen_paraschiv/32/919_2.png) [@Eugen\_Paraschiv](https://discuss.elastic.co/u/Eugen_Paraschiv)\ **Post date:** [December 20, 2014, 11:36am UTC](https://discuss.elastic.co/t/searchparseexception-marvel-no-mapping-found-for-timestamp-in-order-to-sort-on/21250/4 "2014-12-20T11:36:06Z")
The strange thing is that - for some reason, just by leaving it for a couple of hours, it started working. I'm assuming there was some data missing but being written in the marvel index. Thanks, Eugen. On Sat, Dec 20, 2014 at 10:58 AM, Boaz Leskes [b.leskes@gmail.com](mailto:b.leskes@gmail.com) wrote: > I would check your ES installation. This information comes from the Node > Stats API, so it is likely missing there as well. Most of the time this is > caused by missing the Sigar library or some process permission issue. > > Cheers, > Boaz > > On Sunday, December 14, 2014 8:42:22 PM UTC+1, Eugen Paraschiv wrote: > > > One more detail on this - the Marvel UI also displays the exact query > > that's failing. Running that query results in a more informative message - > > probably the root cause of the problem: > > Caused by: org.elasticsearch.search.facet.FacetPhaseExecutionException: > > Facet [fs.total.available\_in\_bytes]: failed to find mapping for fs.total. > > available\_in\_bytes > > And indeed, the _fs.total.available\_in\_bytes_ isn't available in in the > > marvel index. > > Now - the reading is available on _\_nodes/stats_ - so I'm assuming it's > > a mapping problem from Marvel. > > But - I removed the old mapping, restarted the entire cluster and > > basically allowed marvel to re-create the mapping it needs - so that should > > be correct. > > Any help is appreciated. > > Thanks. > > > > On Sunday, December 14, 2014 6:22:22 PM UTC+2, Eugen Paraschiv wrote: > > > > > Hi, > > > I'm using Elasticsearch 1.4.1 and the latest Marvel (1.2.1). > > > I have Marvel installed on every node of the cluster and generating data > > > into the daily index. > > > When going into Marvel, I get the following exception: > > > Caused by: org.elasticsearch.search.SearchParseException: [.marvel- > > > 2014.12.14][0]: from[-1],size[1]: Parse Failure [No mapping found for [ > > > @timestamp] in order to sort on] > > > > > > So - this is referring specifically to the _.marvel-2014.12.14_ index - > > > an index created by Marvel itself, which should thus have the right > > > structure. > > > Am I missing something related to the Marvel setup? > > > Thank you, > > > Eugen. > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/CHat\_7rnqxc/unsubscribe](https://groups.google.com/d/topic/elasticsearch/CHat_7rnqxc/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/81834d9b-546c-4ef9-80d9-a53ba4dd9bc2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/81834d9b-546c-4ef9-80d9-a53ba4dd9bc2%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/81834d9b-546c-4ef9-80d9-a53ba4dd9bc2%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/81834d9b-546c-4ef9-80d9-a53ba4dd9bc2%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- Eugen Paraschiv Consultant, Baeldung Mobile: +40728896170 Blog: [www.baeldung.com](http://www.baeldung.com) Twitter: @baeldung [https://twitter.com/baeldung](https://twitter.com/baeldung) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CA%2BA8vzHgTeRR4p36fAK5z7A%2BmyVQ6EOhZeju8B4zpPvquD8GJg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CA%2BA8vzHgTeRR4p36fAK5z7A%2BmyVQ6EOhZeju8B4zpPvquD8GJg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:42am UTC](https://discuss.elastic.co/t/searchparseexception-marvel-no-mapping-found-for-timestamp-in-order-to-sort-on/21250/5 "2017-07-06T00:42:34Z")