This task has "Unbreak now" priority for two weeks now. Does anybody plan to work on this?

The testing in labs was a bit harsh since it involving disable the slave threads and thus stopping ChronologyProtector from working at all. ChronologyProtector now works across domains as of 85c0f85e925e206 and will wait for the slave to catch up to the point where any local/global user rows where added. A more meaningful test would be proper delayed replication, which requires mysql 5.6.

This problem could still happen if lag is so high that ChronologyProtector gives up (10 sec timeout). Fixing T95501 would help here. I wonder if this error happens during high lag spikes now (the few we have). Would be nice to get logging in place.