It turns out that I had to delete the older indices on elasticsearch
cluster lying around for a very long period of time. After cleaning up some
and restarting the cluster, exceptions in elasticsearch logs have come down
and marvel dashboard is also neat showing the cluster status to be green.
Thanks.
On Tuesday, June 3, 2014 10:36:11 PM UTC-7, Nikhil Mulley wrote:
>
> Thanks for the reply Boaz.
>
> Marvel has been installed as a plugin on all the 4 nodes that I have as
> part of the cluster. Do not see anything specific in ES logs although I see
> plenty of exceptions related to netty, which I am not sure are if anyway
> related to the search parse exceptions on the marvel dashboard.
>
>
> On Monday, June 2, 2014 11:44:47 PM UTC-7, Boaz Leskes wrote:
>>
>> Hi Nikhil,
>>
>> Your ES logs will indicate which field was exactly missing, but I suspect
>> you didn't install Marvel on all your nodes, typically this happens when
>> the master nodes is missing it. Can this be?
>>
>> Cheers,
>> Boaz
>>
>> On Tuesday, June 3, 2014 6:43:13 AM UTC+2, Nikhil Mulley wrote:
>>>
>>> Hi,
>>>
>>> In my elasticsearch cluster, off late on the marvel dashboard there are
>>> searchparseexceptions. Any idea what are these below exceptions mean? They
>>> seem to be happening very recently and even restart of the elasticsearch
>>> service does not seem to help.
>>>
>>> Environment: ElasticSearch 0.90 + LogStash 1.2.1. Java 1.7.0_40
>>>
>>> SearchParseException[[.marvel-2014.06.03][0]: from[-1],size[-1]: Parse
>>> Failure [Failed to parse source
>>> [{"facets":{"0":{"date_histogram":{"key_field":"@timestamp","value_field":"primaries.indexing.index_total","interval":"1m"},"global":true,"facet_filter":{"fquery":{"query":{"filtered":{"query":{"query_string":{"query":"_type:indices_stats"}},"filter":{"bool":{"must":[{"range":{"@timestamp":{"from":1401766706046,"to":"now"}}}]}}}}}}}},"size":50,"query":{"filtered":{"query":{"query_string":{"query":"_type:cluster_event
>>>
>>> OR
>>> _type:node_event"}},"filter":{"bool":{"must":[{"range":{"@timestamp":{"from":1401766706046,"to":"now"}}}]}}}},"sort":[{"@timestamp":{"order":"desc"}},{"@timestamp":{"order":"desc"}}]}]]]
>>>
>>> What is the source that is leading the queries problematic? Is it the
>>> index being corrupt and not useful? Any insight will be helpful.
>>>
>>> Thanks,
>>> Nikhil
>>>
>>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/3b408d05-acf3-4422-bf90-c9c69395c86b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
