MASTER_GTID_WAIT work as documented when executed on a slave,
But if it get trigger on the master it timeout !
- That's wrong because last gtid is from the master and so should exist
- This defeat any naive strategy to load balance read on the master as well .
- This defeat strategy to use same code on a production master-slave with single database deployment for dev