If I remove the -advertise argument there is no problem but the nodes talk each others over pods' IP and since the pods' IP are dynamic there is a possibility for outage scenario. To prevent this I tried to advertise services' IP. It prevents outage scenario and seems work well; however, when I restart 1 node the other nodes logs warning like [WARN] memberlist: Was able to connect to consul-1 but other probes failed, network may be misconfigured .
1- Is this a problem?
2- Can we solve this ?
Regards,
Abdulkadir Dalga
James Phillips
unread,
Sep 28, 2017, 8:12:20 PM9/28/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to consu...@googlegroups.com
Hi,
Sorry for the late reply on this one - did you figure it out? I'm not
I follow what you mean by "I tried to advertise services' IP". Also,
in Consul 0.9.3 we did some work to help Consul servers recover when
their IPs change after a restart, which might also help:
> server: Consul servers can re-establish quorum after all of them change their IP addresses upon a restart. [GH-1580]