are not affected as much. Different companies solve DROP TABLE in different ways. An interesting discussion is found on gh-ost’s repo and on mysql bugs: • https://github.com/github/gh-ost/issues/307 51 http://127.0.0.1:15001/debug/status • vtctld listens on http://127.0.0.1:15000/debug/status • Control panel is available at http://localhost:15000/app/ From within the docker shell, aliases are set up for • freno project page • Mitigating replication lag and reducing read load with freno, a GitHub Engineering blog post 127 Topology Service This document describes the Topology Service, a key part of the

are not affected as much. Different companies solve DROP TABLE in different ways. An interesting discussion is found on gh-ost’s repo and on mysql bugs: • https://github.com/github/gh-ost/issues/307 • https://bugs http://127.0.0.1:15001/debug/status • vtctld listens on http://127.0.0.1:15000/debug/status • Control panel is available at http://localhost:15000/app/ From within the docker shell, aliases are set up for • freno project page • Mitigating replication lag and reducing read load with freno, a GitHub Engineering blog post Topology Service This document describes the Topology Service, a key part of the Vitess

are not affected as much. Different companies solve DROP TABLE in different ways. An interesting discussion is found on gh-ost’s repo and on mysql bugs: • https://github.com/github/gh-ost/issues/307 • https://bugs http://127.0.0.1:15001/debug/status • vtctld listens on http://127.0.0.1:15000/debug/status • Control panel is available at http://localhost:15000/app/ From within the docker shell, aliases are set up for • freno project page • Mitigating replication lag and reducing read load with freno, a GitHub Engineering blog post Topology Service This document describes the Topology Service, a key part of the Vitess

are not affected as much. Different companies solve DROP TABLE in different ways. An interesting discussion is found on gh-ost’s repo and on mysql bugs: • https://github.com/github/gh-ost/issues/307 • https://bugs http://127.0.0.1:15001/debug/status • vtctld listens on http://127.0.0.1:15000/debug/status • Control panel is available at http://localhost:15000/app/ From within the docker shell, aliases are set up for • freno project page • Mitigating replication lag and reducing read load with freno, a GitHub Engineering blog post Topology Service This document describes the Topology Service, a key part of the Vitess

http://127.0.0.1:15001/debug/status • vtctld listens on http://127.0.0.1:15000/debug/status • Control panel is available at http://localhost:15000/app/ From within the docker shell, aliases are set up for • freno project page • Mitigating replication lag and reducing read load with freno, a GitHub Engineering blog post Topology Service This document describes the Topology Service, a key part of the Vitess

auditors and the development team were fluent and incurred no delays. After introductory discussion via mail and video conferencing, the ensuing exchanges took place in a dedicated Slack channel

http://127.0.0.1:15001/debug/status • vtctld listens on http://127.0.0.1:15000/debug/status • Control panel is available at http://localhost:15000/app/ From within the docker shell, aliases are set up for