# Segment node from cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [May 9, 2013, 2:02pm UTC](https://discuss.elastic.co/t/segment-node-from-cluster/11901 "2013-05-09T14:02:34Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Kubes](https://avatars.discourse-cdn.com/v4/letter/k/a9adbd/32.png) [@Kubes](https://discuss.elastic.co/u/Kubes)\ **Post date:** [May 9, 2013, 2:02pm UTC](https://discuss.elastic.co/t/segment-node-from-cluster/11901/1 "2013-05-09T14:02:34Z")
I have a 0.20.6 cluster and want to move to 0.90 and need to test. My plan was to add a new node into the .20 cluster, add replicas for all the shards to the new node, wait for "green", segment the new node from the cluster (break ec2 discovery) and restart the new node, then update. Adding the node and replicating all went fine. The issue I have is when I start the new node without being in the cluster all the shards are unassigned (viewing via head), through the "index" are there? Any ideas why and how to resolve? 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![radu\_gheorghe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/radu_gheorghe/32/556_2.png) [@radu\_gheorghe](https://discuss.elastic.co/u/radu_gheorghe)\ **Post date:** [May 10, 2013, 3:15pm UTC](https://discuss.elastic.co/t/segment-node-from-cluster/11901/2 "2013-05-10T15:15:37Z")
Hello, Any clues in the logs? If not, can you change logging.yml for more verbose logging and see what they say? BTW, another option for migrating might be to start 0.90 on a different cluster, and run a scroll[http://www.elasticsearch.org/guide/reference/api/search/scroll/](http://www.elasticsearch.org/guide/reference/api/search/scroll/)though all your existing data, re-indexing it to your new cluster. ## Best regards, Radu [http://sematext.com/](http://sematext.com/) -- Elasticsearch -- Solr -- Lucene On Thu, May 9, 2013 at 5:02 PM, Kubes [philip@freepricealerts.com](mailto:philip@freepricealerts.com) wrote: > I have a 0.20.6 cluster and want to move to 0.90 and need to test. > > My plan was to add a new node into the .20 cluster, add replicas for all > the shards to the new node, wait for "green", segment the new node from the > cluster (break ec2 discovery) and restart the new node, then update. > > Adding the node and replicating all went fine. The issue I have is when I > start the new node without being in the cluster all the shards are > unassigned (viewing via head), through the "index" are there? > > Any ideas why and how to resolve? > > 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). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:37am UTC](https://discuss.elastic.co/t/segment-node-from-cluster/11901/3 "2017-07-06T02:37:11Z")
Closed on July 6, 2017, 2:37am UTC