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

Start replica with credentials #1449

Open
tfulcrand opened this issue Jun 8, 2022 · 0 comments
Open

Start replica with credentials #1449

tfulcrand opened this issue Jun 8, 2022 · 0 comments

Comments

@tfulcrand
Copy link

Hello to all,

Before asking our question, here is a quick description of our topology. In our environment we have 2 master servers seen as co-master by Orchestrator. Behind each master we have several replica servers dedicated for read queries. All servers use Percona for MySQL 8.0.27 version.
Orchestrator can connect to all servers and offers a good view of our topology espacially when we have replication lag, no replication process, etc.
And when we do a maintenance on one of our master, we usually use Orchestrator to move all replicas from one master to the other in one single drag&drop action (we love this feature). We can use this feature because we set up replication process with credentials like
CHANGE REPLICATION SOURCE TO SOURCE_USER=user1, SOURCE_PASSWORD=password1, ... and then all replication infos are stored in the mysql.slave_master_info table.
But such query generates this kind of messages in error log :
[Warning] [MY-010897] [Repl] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.

To improve our security we decide to remove replication credentials from CHANGE REPLICATION SOURCE (so they aren't stored in the system table) and to pass them in replcation start command : START REPLICA USER=user1 PASSWORD=password1
By doing this, we can't move replicas by drag&drop in Orchestrator (probably because by default Orchestrator run a simple START REPLICA).
So is there a way to tell Orchestrator to use USER and PASSWORD options with START REPLICA statement ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant