Comment 8 for bug 1195628

Daniel thanks now i can see the debug log and found the problem.

I have a server that is a bit multi purpose. It got a standalone mysql for solr (not a slave of the master) and that server also have a open replicator running to get the binlog data for incremental update for elastic search.

now here is the problem, the pt-online-schema-change mistaken my standalone mysql server is a slave of the master and didn't realise in fact it is a java open replicator replicating. so that standalone will never have this new table and then it just stuck forever to wait for that server replicate.

From our server setup point of view, we don't need a seperate server, and also adding new server will add additional cost (of course) so we will not separate the server (not to mention it will require us to change lot of configuration).

For now i will by pass the slave check features with recursion method none, but i think it will be better for the pt-online-schema-change to check that the server is actually a slave.