Error in promotion to master?

Elastic Stack Elasticsearch
3

Got it.

Thanks,
Tal

On Jun 7, 3:57 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

When you use unicast discovery, you need to list (as many as you can) nodes
that will form the cluster. In your case, you should list also
"localhost:9301" and "localhost:9302". Its ok if they are not up, as long as
a node that start up with an existing cluster has at least another node to
ask regarding the state of the cluster.

-shay.banon

On Sun, Jun 6, 2010 at 7:26 PM, Tal talsalm...@gmail.com wrote:

Hi,

I have the following scenario (Windows Vista, Elasticsearch 0.8.0)

Configuration:

discovery.zen.ping.multicast:
enabled: false
discovery.zen.ping.unicast:
hosts: ["localhost:9300"]

  1. Start node A --> It starts as master.
  2. Start node B.
  3. Stop A --> Node B prints that it has been promoted to master.
  4. Start node C.
    Expected behavior: Node C discovers node B as a master.
    Actual Behavior: Node C does not discover B and starts as a new master

Any idea why?
BTW, when I stop node B (A, the master keeps running) and start node C
then node C discovers A as the master.

Thanks,
Tal