Client Node usless after data node fails . Any Solution?

Hi
I am trying to get around the issue of failover by running multiple
instances over same data , by running two elasticsearch instances on a
machine , both having the same data directory , with both nodes being
masters , and 2nd node , not handling the data (node.data=false).

Even if one of the nodes is not a data node, elasticsearch still creates
its directory ([0] , [1]) etc , in the common data directory , (what i
expected was only one sub directory ([0] (only for the data node) ) in the
common directory , with both the nodes being able to search the common
source.

in current case , when both instances are running , the search is fine ,
but when the data node fails , the search returns shards failure exception
, as non-data node searches in it's sub directory([1]) , (which does not
contains the data).

Could somebody please help me resolve the issue ?

Thanks
Tarang Dawer

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

Use two data nodes, and to ensure replication, on two machines.

You can not search or index data on a non-data node. A non-data node
just forwards the request to a data node.

Can you explain why you use two nodes on a single machine? This makes
not much sense.

Jörg

Am 14.05.13 09:46, schrieb Tarang Dawer:

Could somebody please help me resolve the issue ?

--
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.
For more options, visit https://groups.google.com/groups/opt_out.