Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add TiDB single sandbox support #54
Is your feature request related to a problem? Please describe.
I would like to propose
Describe the solution you'd like
TiDB can run with something called
The memory footprint is smaller than MySQL, so it's possible some might even prefer it for development.
Describe alternatives you've considered
I've looked at alternatives installation methods like Homebrew etc, but they do not solve the use case of having multiple versions installed concurrently. The TiDB release schedule is every 6 months, so dbdeployer is really useful in providing a system of organizing binaries for TiDB developers.
I have looked at the initial work, and much of it can be implemented by sandbox templates and some core changes that @datacharmer already has planned (discussed at FOSDEM). Let me try and comment in terms of each:
I will send a pull request after some discussion, but my initial testing shows that the major template changes are:
I believe it will also need to refuse to deploy if neither
Edit: confirmed this bug exists.
I am about to commit the check that will prevent replication, or a deployment without
I've noticed that when I deploy several TiDB sandboxes, the server UUID is always the same(
The implementation is almost finished. To complete it, I'd like to make TiDB installations compatible with MySQL, so that I can include a TiDB deployment in the functional test suite (currently I only have a mock test).
What's missing for integration:
I have created pingcap/tidb#9362 for the port issue and assigned myself.
I didn't think to use socket, but that makes sense to me. Should we also clean up the startup script to delete a stale socket file if there is no tidb-server process to match it? The alternative is to print a warning saying stale socket file.