- Adding an Update Stream document.
- Adding doc for MySQL server protocol.
- Adding a doc for Vitess Sequences.
- Doc on RBR.
- Removing obsolete replication doc.
publish site Tue Jan 24 13:13:41 PST 2017
The new etcd2 topology service is the new more consistent version of the
etcd topology. It has the following improvements:
- Uses the same file structure as zk2topo. It then also uses the generic
vtctld.Explorer as well.
- Uses the new etcd clientv3 library, with new key-value API and leases.
It is not backwards compatible with the old etcd topology.
- Uses a configurable toplevel directory for topology data in global and
local cells.
Vitess 2.1 will still include the old etcd topology client, but it will
be deprecated, and removed from Vitess 2.2. Use topo2topo binary to
upgrade, see documentation.
Implementation details:
- bootstrap.sh now downloads etcd.
- etcd is used in unit tests of the library, instead of using a mock.
- Fixing wrangler.InitTablet error return.
And adding -allow_update to test calls, so they work anyway.
- Running tabletmanager.py for zookeeper, zk2, etcd, etcd2 flavors.
- Ignoring the 'test' tag for vendored libraries. See:
https://github.com/kardianos/govendor#ignoring-build-tags-and-excluding-packages
- in end-to-end tests, restarting etcd to wipe it.
- publish web site.
I'm renaming the PivotSchemaChanges.md into SchemaSwap.md, modifying it to
describe the current schema swap process and reformatting to be easier to read
in an editor.
I'm also modifying the replication docs to mention schema swap instead of pivot,
and to correct a few not quite factually correct statements.
The site needed publishing after #2312 and maybe after some other changes.
On the way I fixed a couple of incorrect things in vtctl docs (typo in an error
message and change of tablet type name WORKER->DRAINED that happened in #2151).
We'll switch serving vitess.io:
- before: from the gh-pages branch
- now: from the docs directory out of the master branch
This way it is much easier to update the website:
- no switching between branches required
- no untracked files get in our way in the gh-pages branch
- generated pages can be written in place and do not have to be moved around
- website can be updated and published in the same pull request