Happy new year and happy new decade! How did our contributors wrap up the decade? Let’s take a look, and then take a peek at what’s coming this year!
This month our team made 4 TiKV releases - 3.0.x and 2.1.x releases are minor releases, and 3.1.0-beta is our upcoming next major release before 4.0.
You can review the changelogs here:
Upgrading? Here’s things you should know:
- In 3.0.8 we reduced the severity of errors occuring in the coprocessor to
- In 3.0.8 the default value of
falseto help reduce region creation pressure during table creation/deletion.
- In 3.0.8 we now welcome you to experiment with a new feature to get flame graphs from a running TiKV. Try visiting
$SERVER:20180/debug/pprof/profile?seconds=10to see a flamegraph of that TiKV. We’ll be adding more details to our documentation about this soon!
- Version 3.1.0 is a beta and should not be adopted in production deployments. Please do try it out and let us know if you find issues. It includes new follower read and backup/restore features.
TiKV 3.1.0 is now in beta, with a stable release coming soon! This includes new major features like follower read and distributed backup/restore.
Follower read will allow clients to read data from followers in a region, reducing pressure on the region leader. Distributed backup and restore are a long awaited feature to make it more practical and efficient to both prepare for the worst, and handle it if it does happen.
Tang Liu wrote an in depth article about how TiKV handles read and write operations over on the TiKV blog.
Yuanli Wang wrote about recent work on AutoTiKV, an AI-powered tuning tool for DBAs to help them find the ideal workload settings for their TiKVs.
Back in October Dongxu Haung wrote about how TiDB is using TiKV’s pessimistic transaction feature. We missed it then, so as part of a “better late than never” idea, we’ve included it here.
- @iosmanthus taught TiKV about a new option,
- @rustin-liu opened a number of coprocessor PRs to add new functionality like
- @yiwu-arbug added the beginnings of external S3 storage support in #6209.
- @brson has been continuing work on the Engine abstraction. Including work like #6122 which parameterizes parts TiKV over
- @renkai localized some server metrics in #6258.
- @sticnarf taught the coprocessor to use
- @nrc landed a sequence of PRs to do some refactoring in the transaction module. Including #6272 and #6246.
- Several new issues like #6281, #6191, #6316 and #6368 were created, asking for help tackling several improvements in the coprocessor.
- @zhouqiang-cl noticed in #6180 we weren’t running some tests on the CI, but they were run with
- @iosmanthus found in #6145 that some
cargocommands were’t working due to our use of features. @koushiro has some clever fixes in #6317 to keep TiKV working with default
cargocommands, what a great job!
This January we’ll be starting to hammer out our grand plans for 2020. This year will likely include both a 3.1 and 4.0 release of TiKV. 3.1.0 will include new features we wrote about above, and 4.0.0 will include even more things from the roadmap.
If any of these projects sound like something you’d like to contribute to, let us know on our chat and we’ll try to help you get involved.
We’d like to welcome the following new contributors to TiKV and thank them for their work!
If you’d like to get involved, we’d love to help you get started. You might be interested in tackling one of these issues. If you don’t know how to begin, please leave a comment and somebody will help you out. We’re also very keen for people to contribute documentation, tests, optimizations, benchmarks, refactoring, or other useful things.
This Week in TiDB
For more detailed and comprehensive information about TiDB and TiKV, we have weekly updates. The following cover $MONTH: