On Sat, May 01, 2021 at 02:55:41AM +0200, Ilya Maximets wrote: > Replication can be used to scale out read-only access to the database. > But there are clients that are not read-only, but read-mostly. > One of the main examples is ovn-controller that mostly monitors > updates from the Southbound DB, but needs to claim ports by sending > transactions that changes some database tables. > > Southbound database serves lots of connections: all connections > from ovn-controllers and some service connections from cloud > infrastructure, e.g. some OpenStack agents are monitoring updates. > At a high scale and with a big size of the database ovsdb-server > spends too much time processing monitor updates and it's required > to move this load somewhere else. This patch-set aims to introduce > required functionality to scale out read-mostly connections by > replication. > > Replication mode natively supports replication of standalone and > clustered databases, so it will work for any type of OVN deployment.
I think that this series has the details that one needs to understand it at a high level, but I didn't see a high-level overview of its intended use. I think the idea is that, for a use case like OVN, one would deploy a clustered OVS database, and then the second tier would be a collection of replicas on top of that cluster. If that's the case, I think that adding a paragraph to an appropriate high-level documentation file for OVSDB explaining it would be helpful, and possibly a (ASCII art?) diagram. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
