Yes it is the same version. 1.1.0.
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Marvel-dashboard-not-showing-Nodes-and-other-info-tp4064098p4064219.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.
--
You received this message
yed marvel in our setup. It was working fine. Then there was
> an
> issue with cluster and one of query nodes left. We restarted service on
> query nodes and till them we are seeing Marvel dashboard showing following
> error,
>
>
> SearchParseException[[.marvel-2014.09.26][0]:
We have deployed marvel in our setup. It was working fine. Then there was an
issue with cluster and one of query nodes left. We restarted service on
query nodes and till them we are seeing Marvel dashboard showing following
error,
SearchParseException[[.marvel-2014.09.26][0]: from[-1],size[-1
Hi,
The marvel overview by default shows 20 indices (third panel)
I guess there is some way to configure this 20? To say 40?
But how to do it?
Your help appreciated.
Regards.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe f
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
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
gt;
> 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.
>
>
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
