| Bug #50604 | No way to disable use of the master.info file for replication topology discovery | ||
|---|---|---|---|
| Submitted: | 25 Jan 2010 20:22 | Modified: | 6 Jul 2010 13:26 |
| Reporter: | Mark Leith | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Agent | Severity: | S3 (Non-critical) |
| Version: | 2.1.0.1096 | OS: | Any |
| Assigned to: | Michael Schuster | CPU Architecture: | Any |
| Tags: | master.info, topology discovery, windmill | ||
[25 Jan 2010 20:22]
Mark Leith
[25 Jan 2010 21:16]
Mark Leith
Copied from Bug#50298: [15 Jan 9:09] Simon Mudd Please understand why I'm writing this comment in here. AFAIK the agent currently uses this information to try and get the slave's replication credentials and then to login to the master server using those credentials to get information on mysql.inventory. This is extremely bad etiquette, impersonating another "user". The mysqld replication user is supposed to be talking to the master with these credentials. If the agent wants to talk to the master then it should be given specific credentials to obtain the specific information it needs. Unfortunately this information is currently not available to the agent. Therefore I would recommend rather than look for the mysqld's master.info file you fix the agent and ensure that the DBA/sysadmin provides credentials to access the master server. Current behaviour is very antisocial. I have already complained about this before in the Enterprise ticketing system, but you guys don't "get it". Give me your credit card numbers and let me go shopping.... PLEASE fix the behaviour cleanly and if nothing else login with the username provided by the current agent credentials, and to the master server as provided by the master.info. That at least is slightly better.
[15 Mar 2010 23:01]
Enterprise Tools JIRA Robot
Andy Bang writes: Included in build 2.2.0.1651
[16 Apr 2010 11:47]
Enterprise Tools JIRA Robot
Mark Leith writes: Sorry for the confusing initial description, we also need an option to totally disable master_uuid based discovery. Something such as: [replication] discovery-enabled = 1|0
[10 May 2010 19:57]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch installed in versions => 2.2.1.1714.
[5 Jul 2010 16:52]
Enterprise Tools JIRA Robot
Bill Weber writes: resolving so it can be documented
[6 Jul 2010 13:26]
MC Brown
A note has been added to the 2.2.0 changelog:
To aid in the replication discovery performed by the agent, you
can now provide alternative credentials for connecting to the
replication master to obtain the master UUID created by
&merlin;. The master UUID enables &merlin_agent; to more easily
identify and reconcile the master. You set these options on an
instance basis, and setting the options prevents the agent using
the <filename>master.info</filename> to determine the master
UUID.
A note has been added to the 2.2.1 changelog:
The methods for replication discovery by &merlin_agent; have
been modified. A new option for &merlin_agent; has been added
that prevents the master UUID being used in the replication
topology determination. This also prevents &merlin_agent; from
obtaining replication information from the
<filename>master.info</filename> file.
[6 Jul 2010 17:59]
Andrii Nikitin
To disable using information from master.info place agent-master-uuid-discover=0 into [mylsq-proxy] section of file agent/etc/mysql-monitor-agent.ini :
