Add another node (master only : data false) with minimal HEAP and set minimum master nodes to 2 or set minimum master nodes to 2 but in that case your cluster will stop working in case of failure of any node or network failure
-- David Pilato - Developer | Evangelist elastic.co @dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr <https://twitter.com/elasticsearchfr> | @scrutmydocs <https://twitter.com/scrutmydocs> > Le 28 mai 2015 à 10:40, prakhar <prakhar.mishra1...@gmail.com> a écrit : > > I am using *Elasticsearch 1.5.2* and trying to setup a 2-node cluster. These > 2 nodes are primarily for failover strategy (if any one node goes down, the > other one is still there to handle requests), I don't need to divide primary > shards or something like that, (total data is no more than 500mb on > hard-disk). > > Everything goes well, until *Split Brains* thing kicks in. Now, since I > don't have much data, I don't feel any requirement of 3 nodes. And I want to > have failover mechanism too. Which means, > /discovery.zen.minimum_master_nodes/ cannot be more than /1/. > > Now, I have two questions: > > 1. Is there any configuration possible, which could overcome *2 master > nodes* or *Split Brains *problem? > 2. If not, what all other options do I have to make it work? Like, keeping > both in different clusters (one online, other one offline) and updating > offline with online, time to time, for the time when online cluster goes > down. Or, do I have to go for 3-node cluster? > > I am going on production environment. Please help. > > Env Info: Two machines (VMWare driven), having 4 cores, 8gb RAM and CentOS. > We are firing 7-8 queries (1 /_search/ and other /_count/) per search. > Indexing op won't be very frequent (until we sync existing indices from DB > through /_bulk/ API), but searching is going to be quite frequent. > > > > -- > View this message in context: > http://elasticsearch-users.115913.n3.nabble.com/Elasticsearch-2-node-cluster-with-failover-tp4074949.html > Sent from the Elasticsearch Users mailing list archive at Nabble.com. > > -- > Please update your bookmarks! We have moved to https://discuss.elastic.co/ > --- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/1432802400465-4074949.post%40n3.nabble.com. > For more options, visit https://groups.google.com/d/optout. -- Please update your bookmarks! We have moved to https://discuss.elastic.co/ --- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/42DC41A9-8F90-4BB9-BBBC-35D57105A809%40pilato.fr. For more options, visit https://groups.google.com/d/optout.
