Boaz,
Thanks for the response; I checked on it late yesterday, and it seems to have
righted itself somehow. I brought up another cluster this morning, and it
immediately received all the node & index data properly, so I must have gotten
something stuck on my first try.
Thanks for the response!
Jeff,
Two things can be at play:
1) Either you have no data (easily checked by direct call to the monitoring
cluster, from Sense or curl )
2) Or something is wrong with the mapping - typically caused by missing an
index template. Can you check wether your monitoring cluster has GET
_template/
I'm experiencing a similar issue to this. We have two clusters:
- 2 node monitoring cluster (1 master/data & 1 just data)
- 5 node production cluster (2 data, 3 masters)
The output below is from the non-master data node of the Marvel monitoring
cluster. There are no errors being reporte
Are there any marvel errors on one of the data nodes that marvel is getting
the data from? Usually you error means marvel could not ship the data over
to the monitoring cluster.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe f
Error log in the monitoring node:
**
[2014-05-28 17:28:20,009][DEBUG][action.search.type ] [MarvelSE02]
[.marvel-2014.05.28][2], node[44R9_5vfRVmEJDgApyBRrQ], [P], s[STARTED]:
Failed to execute [org.elasticsearch.action.search.SearchRequest@6c4e0d81]
lastShard [true]
org
Hi,
We have development test cluster 8 nodes running on 0.90.10 ES. Also we
have one monitoring node separated from dev cluster for marvel.
We installed all nodes to marvel latest /1.1.1/ pointing to monitoring
marvel IP in the ES config. Told the monitoring node not collect its data.
We
