-
Notifications
You must be signed in to change notification settings - Fork 926
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
Discovery doesn't discover in extremely simple setup #1492
Comments
unixtastic
changed the title
Discovery doesn't discover is extremely simple setup
Discovery doesn't discover in extremely simple setup
Sep 9, 2023
The test above was with AWS instances. I see the exact same issue with digital ocean VMs with all hostnames in /etc/hosts.
|
Using a mysql 8 orchestrator backend instead of sqlite behaves the same way. |
设置两个地方:
|
The changes suggested by jxs-2022 fixed it. I suggest updating the documentation. If anyone can suggest a more active fork of this project I'd be grateful. I don't think anyone is approving PRs here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Orchestrator discovery only functions if manually run on all nodes starting at the master and working down the tree. I tried Orchestrator 3.2.6 on Ubuntu 18.04 and 22.04. All test Mysql servers are Percona 5.7.43-47 and are correctly replicating.
orchestrator.conf.json:
mysql.cnf:
Mysql server_id and UUID is unique for each server.
If I turn debug on I see orchestrator is pulling information from SHOW SLAVE HOSTS on the master:
Yet the topology only lists the master and none of it's slaves:
The user account for orchestrator and the account for replication is correctly setup on all servers.
The text was updated successfully, but these errors were encountered: