# Is re-election/assignment of the master node possible? **URL:** \ **Category:** Elasticsearch\ **Created:** [November 26, 2014, 8:47pm UTC](https://discuss.elastic.co/t/is-re-election-assignment-of-the-master-node-possible/20960 "2014-11-26T20:47:36Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Erik\_theRed](https://avatars.discourse-cdn.com/v4/letter/e/fbc32d/32.png) [@Erik\_theRed](https://discuss.elastic.co/u/Erik_theRed)\ **Post date:** [November 26, 2014, 8:47pm UTC](https://discuss.elastic.co/t/is-re-election-assignment-of-the-master-node-possible/20960/1 "2014-11-26T20:47:36Z")
Is there any notion triggering a re-election of the master node? I'm currently running 1.2.4, and I have an instance that is scheduled for retirement (my favorite!) and it just so happens that it's my master node. What can I do to avoid the dreaded "RED" state? Is there some mechanism that can allow me to re-assign the current master to one of the other available two dedicated master nodes so I can reboot the current master? I ask because I'm a bit gun-shy due to my experience when an elected master node has gone unresponsive (before I created dedicated masters) due to excessive HTTP connections, master re-election seemed to never occur and everything comes crumbling down. Thanks! - Erik -- 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/80d7ec69-40e6-46d6-8de1-159d6117a7c7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/80d7ec69-40e6-46d6-8de1-159d6117a7c7%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [November 26, 2014, 8:57pm UTC](https://discuss.elastic.co/t/is-re-election-assignment-of-the-master-node-possible/20960/2 "2014-11-26T20:57:58Z")
On Wed, Nov 26, 2014 at 3:47 PM, Erik theRed [j.e.redding@gmail.com](mailto:j.e.redding@gmail.com) wrote: > Is there any notion triggering a re-election of the master node? > > I'm currently running 1.2.4, and I have an instance that is scheduled for > retirement (my favorite!) and it just so happens that it's my master node. > What can I do to avoid the dreaded "RED" state? Is there some mechanism > that can allow me to re-assign the current master to one of the other > available two dedicated master nodes so I can reboot the current master? Move all the shards off of the node using allocation include/exclude settings. If you shoot the master one of the other master eligible nodes will take over quickly and there won't be any interruptions. > I ask because I'm a bit gun-shy due to my experience when an elected > master node has gone unresponsive (before I created dedicated masters) due > to excessive HTTP connections, master re-election seemed to never occur and > everything comes crumbling down. I've never had that problem. My cluster is pretty small though - only 31 nodes. Nik -- 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/CAPmjWd2qctbbzPgH4iKTw1TvRymCL125zXymAeFUo9%3D84COLXg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd2qctbbzPgH4iKTw1TvRymCL125zXymAeFUo9%3D84COLXg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Erik\_theRed](https://avatars.discourse-cdn.com/v4/letter/e/fbc32d/32.png) [@Erik\_theRed](https://discuss.elastic.co/u/Erik_theRed)\ **Post date:** [November 26, 2014, 9:11pm UTC](https://discuss.elastic.co/t/is-re-election-assignment-of-the-master-node-possible/20960/3 "2014-11-26T21:11:12Z")
Thanks, Nik - There's no data on the node so it sounds like master reelection should fail over fairly quickly. On Wednesday, November 26, 2014 2:58:43 PM UTC-6, Nikolas Everett wrote: > On Wed, Nov 26, 2014 at 3:47 PM, Erik theRed \<[j.e.r...@gmail.com](mailto:j.e.r...@gmail.com) > \\> wrote: > > > Is there any notion triggering a re-election of the master node? > > > > I'm currently running 1.2.4, and I have an instance that is scheduled for > > retirement (my favorite!) and it just so happens that it's my master node. > > What can I do to avoid the dreaded "RED" state? Is there some mechanism > > that can allow me to re-assign the current master to one of the other > > available two dedicated master nodes so I can reboot the current master? > > Move all the shards off of the node using allocation include/exclude > settings. If you shoot the master one of the other master eligible nodes > will take over quickly and there won't be any interruptions. > > > I ask because I'm a bit gun-shy due to my experience when an elected > > master node has gone unresponsive (before I created dedicated masters) due > > to excessive HTTP connections, master re-election seemed to never occur and > > everything comes crumbling down. > > I've never had that problem. My cluster is pretty small though - only 31 > nodes. > > Nik -- 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/b9506885-e321-4abe-b1c2-db0d802b07ec%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b9506885-e321-4abe-b1c2-db0d802b07ec%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Norberto\_Meijome](https://avatars.discourse-cdn.com/v4/letter/n/ed655f/32.png) [@Norberto\_Meijome](https://discuss.elastic.co/u/Norberto_Meijome)\ **Post date:** [November 27, 2014, 5:59pm UTC](https://discuss.elastic.co/t/is-re-election-assignment-of-the-master-node-possible/20960/4 "2014-11-27T17:59:22Z")
The load issue affecting master detection / election shouldn't happen if you have dedicated masters... At least it is with 0.90.x ( with my limited knowledge of ES implementation details, there seems to be a lock or priority issue when serving large # of requests (http / thrift) , affecting cluster / metadata updates... I would think these metadata tasks ought to take priority in some cases over queries... ) On 26/11/2014 6:11 pm, "Erik theRed" [j.e.redding@gmail.com](mailto:j.e.redding@gmail.com) wrote: > Thanks, Nik - > > There's no data on the node so it sounds like master reelection should > fail over fairly quickly. > > On Wednesday, November 26, 2014 2:58:43 PM UTC-6, Nikolas Everett wrote: > > > On Wed, Nov 26, 2014 at 3:47 PM, Erik theRed [j.e.r...@gmail.com](mailto:j.e.r...@gmail.com) wrote: > > > > > Is there any notion triggering a re-election of the master node? > > > > > > I'm currently running 1.2.4, and I have an instance that is scheduled > > > for retirement (my favorite!) and it just so happens that it's my master > > > node. What can I do to avoid the dreaded "RED" state? Is there some > > > mechanism that can allow me to re-assign the current master to one of the > > > other available two dedicated master nodes so I can reboot the current > > > master? > > > > Move all the shards off of the node using allocation include/exclude > > settings. If you shoot the master one of the other master eligible nodes > > will take over quickly and there won't be any interruptions. > > > > > I ask because I'm a bit gun-shy due to my experience when an elected > > > master node has gone unresponsive (before I created dedicated masters) due > > > to excessive HTTP connections, master re-election seemed to never occur and > > > everything comes crumbling down. > > > > I've never had that problem. My cluster is pretty small though - only 31 > > nodes. > > > > Nik > > -- > 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/b9506885-e321-4abe-b1c2-db0d802b07ec%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b9506885-e321-4abe-b1c2-db0d802b07ec%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/b9506885-e321-4abe-b1c2-db0d802b07ec%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b9506885-e321-4abe-b1c2-db0d802b07ec%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CACj2-4J8Ycj07jhHdX71JJjAHW0\_ZALMH9mPUcW1\_\_sF\_1NagA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACj2-4J8Ycj07jhHdX71JJjAHW0_ZALMH9mPUcW1__sF_1NagA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![CaryUrive](https://avatars.discourse-cdn.com/v4/letter/c/a183cd/32.png) [@CaryUrive](https://discuss.elastic.co/u/CaryUrive)\ **Post date:** [November 28, 2014, 9:31am UTC](https://discuss.elastic.co/t/is-re-election-assignment-of-the-master-node-possible/20960/5 "2014-11-28T09:31:37Z")
As soon as we surf the internet and looking for the jammer products we can see that there are various types of signal jammers that are for sale in the market now such as the mobile phone jammers, **[gps jammers](http://www.jammerinthebox.com/categories/GPS_Signal_Jammer/)**, wifi jammers, UHF jammers, the multi-functional signal jammers and so many others kinds of signal jammers for sale as well. And what people now need to do is just select the best one according to their needs. ---
**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:47am UTC](https://discuss.elastic.co/t/is-re-election-assignment-of-the-master-node-possible/20960/6 "2017-07-06T00:47:11Z")