pt-slave-find does not report with MySQL sandbox

Bug #1002512 reported by Ronald Bradford
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to

Bug Description

Using MySQL Sandbox with a standard replication topology, pt-slave-find states there are 2 slaves connected but does not print any details as expected with tool.

$ pt-slave-find --defaults-file=master/my.sandbox.cnf --host localhost --report-format summary
Version 5.5.24-log
Server ID 1
Uptime 22:45 (started 2012-05-21T16:33:12)
Replication Is not a slave, has 2 slaves connected,
                is not read_only
Binary logging STATEMENT
Slave status
Slave mode STRICT
Auto-increment increment 1, offset 1
InnoDB version 1.1.8

Full setup instructions

$ wget
$ tar xvfz MySQL-Sandbox-3.0.25.tar.gz
$ cd MySQL-Sandbox-3.0.25
$ perl Makefile.PL
$ make
$ make test
$ sudo make install
$ make_sandbox --help
$ mkdir -p $HOME/opt/mysql
$ cd $HOME/opt/mysql
$ wget
$ tar xvfz mysql-5.5.24-linux2.6-x86_64.tar.gz
$ mv mysql-5.5.24-linux2.6-x86_64 5.5.24
$ make_replication_sandbox 5.5.24
$ cd $HOME/sandbox/rsandbox_5_5_24

tags: added: pt-slave-find wrong-output
Changed in percona-toolkit:
status: New → Triaged
Brian Fraser (fraserbn)
Changed in percona-toolkit:
assignee: nobody → Brian Fraser (fraserbn)
Revision history for this message
Brian Fraser (fraserbn) wrote :

There's two bugs here. First is that even though the server is on a nonstandard port, we incorrectly pick --recursion-method processlist. So until this is fixed, people should be able to work around this by using an explicit --port or dsn on their command lines.
The second bug is that MySQL Sandbox sets report-host to a fake hostname, so even with --recursion-method hosts, it still fails (and hangs!). No clue what to do here.

Brian Fraser (fraserbn)
Changed in percona-toolkit:
status: Triaged → In Progress
Brian Fraser (fraserbn)
Changed in percona-toolkit:
milestone: none → 2.1.7
Revision history for this message
Brian Fraser (fraserbn) wrote :

Apparently setting report-host to a fake hostname isn't a normal pattern, so we're just not going to fix that, at least until there's a compelling reason to do so.

If someone is affected by that, feel free to create a new ticket?

Changed in percona-toolkit:
milestone: 2.1.7 → 2.1.8
Changed in percona-toolkit:
milestone: 2.1.8 → none
Changed in percona-toolkit:
status: In Progress → Triaged
assignee: Brian Fraser (fraserbn) → nobody
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Other bug subscribers