All shards are created equally. Elasticsearch promotes replica automatically to primaries if necessary. So there is no reason for any headache around primary/replica locations, ES manages node disaster automatically.
Jörg On Mon, Mar 2, 2015 at 8:46 PM, Davinder Deol <[email protected]> wrote: > We have a requirement where we want to create a node and ask it to join > the cluster. But we don't want this node to have primary shard. > > it is like a Disaster scenario where I have a node running on disaster > server but that node will never have primary shards of my index. It can > only have replica of my index. > > So we looking for a way to configure node or index to control where to > place primary and replica shards? > > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/4c08df2e-3050-49ce-a741-963d2b2a4050%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/4c08df2e-3050-49ce-a741-963d2b2a4050%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGmJJrBL%3DfgY32tquA7r1kJVEj-r6yBRADOmMFNCzfkNA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
