pt-slave-find doesn't indicate master-master

Bug #1177035 reported by Jay Janssen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Confirmed
Undecided
Unassigned

Bug Description

For example:

# pt-slave-find localhost
localhost
Version 5.5.30-30.2-log
Server ID 1242
Uptime 9+18:46:30 (started 2013-04-27T02:36:24)
Replication Is a slave, has 7 slaves connected, is not read_only
Filters replicate_ignore_table=shbdn.sessions; replicate_ignore_db=pma
Binary logging MIXED
Slave status 0 seconds behind, running, no errors
Slave mode STRICT
Auto-increment increment 2, offset 2
InnoDB version 5.5.30-rel30.2
....
+- 192.168.1.75
   Version 5.5.30-30.2-log
   Server ID 175
   Uptime 9+18:46:35 (started 2013-04-27T02:36:19)
   Replication Is a slave, has 1 slaves connected, is read_only
   Filters replicate_ignore_table=shbdn.sessions; replicate_ignore_db=pma
   Binary logging MIXED
   Slave status 0 seconds behind, running, no errors
   Slave mode STRICT
   Auto-increment increment 2, offset 1
   InnoDB version 5.5.30-rel30.2

.75 is actually a dual-master of localhost, but nothing shows that.

Revision history for this message
Daniel Nichter (daniel-nichter) wrote :

What do you mean by "dual master"? .75 has 2 slaves but neither are shown?

tags: added: pt-slave-find
Revision history for this message
Jay Janssen (jay-janssen) wrote : Re: [Bug 1177035] Re: pt-slave-find should more clearly show dual-masters

On Jun 20, 2013, at 12:45 PM, Daniel Nichter <email address hidden> wrote:

> What do you mean by "dual master"? .75 has 2 slaves but neither are
> shown?

dual master = two masters in circular replication.

I truncated the output, but it would be nice if it was clear that .75 was also a master to localhost.

Jay Janssen, MySQL Consulting Lead, Percona
http://about.me/jay.janssen

summary: - pt-slave-find should more clearly show dual-masters
+ pt-slave-find doesn't indicate master-master
Changed in percona-toolkit:
status: New → Confirmed
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1108

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.