tdunning commented on issue #1048: ZOOKEEPER-3188: Improve resilience to network URL: https://github.com/apache/zookeeper/pull/1048#issuecomment-539580943 On Tue, Oct 8, 2019 at 8:45 AM Andor Molnár <notificati...@github.com> wrote: > *...* > @symat <https://github.com/symat> I experienced something weird with this > patch. Tried the following: > > I'm having 2 network interfaces in my Mac: wifi + cable, connected with 2 > different IPs. Created the following config: > > server.1=172.30.64.161:3181:4181|172.30.65.130:3181:4181 > server.2=172.30.64.161:3182:4182|172.30.65.130:3182:4182 > server.3=172.30.64.161:3183:4183|172.30.65.130:3183:4183 > > At the beginning both interfaces were up. When I started ZK quorum, it > connected successfully and quorum was up within a second. When I disabled > the cable interface (pulling the cable out), the nodes started to > communicate on the other interface. > > After that I swapped the interfaces (cable plugged in, wifi disabled) and > nodes went back to looking state and were not able to form a quorum again. > Not even after a restart! > > Maybe this is not a real life scenario which this patch should be prepared > for, but I'm not sure. > This is absolutely a real-life scenario and it should work. If I were doing this, I would be suspicious that something about what I was seeing wasn't really working the way I thought. In the zeroth scenario (both interfaces live), how do you verify which link is being used? What traffic is observed on the wifi side even when it is ostensibly not used? In your second scenario (wifi-disabled), can you ssh from one node to another?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
