nodes in Cluster A are feeding Marvel data to the monitoring node in
Cluster B.
2 primary shards are spread to 2 data nodes but replica shards are stuck in
unassigned state (waited over an hour)
There is no error in the log. What am i doing wrong?
Previously we just deleted indices because they were just marvel data but
we can't keep doing it when we go into production.
Thanks!
I assume you mean that shards of the .marvel- indices are left unassigned?
If so, that's because your marvel cluster has 1 node so there is no place
to put the replicas. This is fine, as long as you understand that losing
that monitoring node may mean loosing the collected monitoring data.
I also wonder if you have set the following line in you monitor node
elasticsearch.yml file:
marvel.agent.enabled: false
This is needed to stop marvel from collecting data from the monitoring node
as well, which will lead to confusion.
Cheers,
Boaz
On Thursday, September 4, 2014 3:06:14 AM UTC+2, kti...@hotmail.com wrote:
Here is my node setup:
Cluster A
1 master
1 query
2 data
Cluster B
1 monitor
nodes in Cluster A are feeding Marvel data to the monitoring node in
Cluster B.
2 primary shards are spread to 2 data nodes but replica shards are stuck
in unassigned state (waited over an hour)
There is no error in the log. What am i doing wrong?
Previously we just deleted indices because they were just marvel data but
we can't keep doing it when we go into production.
Thanks!
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.