# Unassigned replica shard stuck in that state **URL:** \ **Category:** Elasticsearch\ **Created:** [September 4, 2014, 1:06am UTC](https://discuss.elastic.co/t/unassigned-replica-shard-stuck-in-that-state/19613 "2014-09-04T01:06:14Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kti\_sk](https://avatars.discourse-cdn.com/v4/letter/k/c4cdca/32.png) [@kti\_sk](https://discuss.elastic.co/u/kti_sk)\ **Post date:** [September 4, 2014, 1:06am UTC](https://discuss.elastic.co/t/unassigned-replica-shard-stuck-in-that-state/19613/1 "2014-09-04T01:06:14Z")
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! -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/6d1240c5-018d-4a2f-9b79-ad6fbabc8c31%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6d1240c5-018d-4a2f-9b79-ad6fbabc8c31%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [September 28, 2014, 6:22pm UTC](https://discuss.elastic.co/t/unassigned-replica-shard-stuck-in-that-state/19613/2 "2014-09-28T18:22:18Z")
Hi, 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](mailto: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! -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/34713a43-f984-4555-a43a-5b11725df53a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/34713a43-f984-4555-a43a-5b11725df53a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:59am UTC](https://discuss.elastic.co/t/unassigned-replica-shard-stuck-in-that-state/19613/3 "2017-07-06T00:59:29Z")