Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DocDB] Public IP deployment "Error retrieving leader master URL" from the master UI follower in another zone #11603

Closed
FranckPachot opened this issue Feb 28, 2022 · 2 comments
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug priority/medium Medium priority issue

Comments

@FranckPachot
Copy link
Contributor

FranckPachot commented Feb 28, 2022

Jira Link: [DB-361](https://yugabyte.atlassian.net/browse/DB-361)

Description

I'm deploying a lab with two zones across public IP between two zones:

zone           public IP        private IP

eu-fra-1-ad-3  yb1.pachot.net   10.0.0.231
eu-fra-1-ad-3  yb2.pachot.net   10.0.0.200

eu-zrh-1-ad-1  yb3.pachot.net   10.0.0.14

with the following:

ssh -q [email protected] /home/opc/yugabyte/bin/yb-master --master_addresses=10.0.0.231:7100,yb2.pachot.net:7100,yb3.pachot.net:7100 --server_broadcast_addresses=yb1.pachot.net:7100 --rpc_bind_addresses=10.0.0.231:7100 --use_private_ip=zone --placement_cloud oci --placement_region eu-fra-1 --placement_zone eu-fra-1-ad-3 --fs_data_dirs=/home/opc/var/data --replication_factor=3 --default_memory_limit_to_ram_ratio=0.20  </dev/null &
ssh -q [email protected] /home/opc/yugabyte/bin/yb-master --master_addresses=yb1.pachot.net:7100,10.0.0.200:7100,yb3.pachot.net:7100 --server_broadcast_addresses=yb2.pachot.net:7100 --rpc_bind_addresses=10.0.0.200:7100 --use_private_ip=zone --placement_cloud oci --placement_region eu-fra-1 --placement_zone eu-fra-1-ad-3 --fs_data_dirs=/home/opc/var/data --replication_factor=3 --default_memory_limit_to_ram_ratio=0.20  </dev/null &
ssh -q [email protected] /home/opc/yugabyte/bin/yb-master --master_addresses=yb1.pachot.net:7100,yb2.pachot.net:7100,10.0.0.14:7100 --server_broadcast_addresses=yb3.pachot.net:7100  --rpc_bind_addresses=10.0.0.14:7100 --use_private_ip=zone --placement_cloud oci --placement_region eu-zrh-1 --placement_zone eu-zrh-1-ad-1 --fs_data_dirs=/home/opc/var/data --replication_factor=3 --default_memory_limit_to_ram_ratio=0.20   </dev/null &

It looks good but http://yb3.pachot.net:7000/ shows:

Error retrieving leader master URL: http://10.0.0.200:7000/?raw
Error: Network error (yb/util/curl_util.cc:55): curl error: Couldn't connect to server.

and in my opinion, this should use the public IP because the leader (http://yb2.pachot.net:7000/) is accessible though public IP only. The other follower (http://yb1.pachot.net:7000/) can show the UI because it is in the same zone as the leader.

@FranckPachot FranckPachot added the area/docdb YugabyteDB core features label Feb 28, 2022
@bmatican
Copy link
Contributor

bmatican commented Mar 2, 2022

This is likely the same problem as with #7867
We should probably use the server_broadcast_address, if one is specified.

@druzac
Copy link
Contributor

druzac commented May 16, 2022

This should be fixed by e99e29481e596b53d9261096457829eccc3c253f.

@druzac druzac closed this as completed May 16, 2022
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels May 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug priority/medium Medium priority issue
Projects
None yet
Development

No branches or pull requests

4 participants