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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/71932dba-a12f-4b48-874b-c51fc660dbd2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e2f43a38-3062-4253-a519-38b3bb3c1c1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/81834d9b-546c-4ef9-80d9-a53ba4dd9bc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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 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.
To unsubscribe from this group and all its topics, send an email to
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?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
Eugen Paraschiv
Consultant, Baeldung
Mobile: +40728896170
Blog: www.baeldung.com
Twitter: @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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CA%2BA8vzHgTeRR4p36fAK5z7A%2BmyVQ6EOhZeju8B4zpPvquD8GJg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.