[ovs-discuss] Regarding Clustered OVSDB

Rutuja Umesh Madhure rutujaumesh.madhure at nutanix.com
Mon Jul 26 03:16:15 UTC 2021

Thank you very much for the information.

Rutuja Madhure
From: Ilya Maximets <i.maximets at ovn.org>
Sent: Friday, July 23, 2021 9:56 PM
To: ovs-discuss at openvswitch.org <ovs-discuss at openvswitch.org>; Rutuja Umesh Madhure <rutujaumesh.madhure at nutanix.com>
Cc: i.maximets at ovn.org <i.maximets at ovn.org>
Subject: Re: [ovs-discuss] Regarding Clustered OVSDB

> Hi,
> It would be really helpful if you could address the below questions:
>   1.  Is there a way for the client to know the leader ovsdb server IP
>       in a clustered ovsdb model (other than from the logs)?

Client knows if it's connected to a leader or not by monitoring the
_Server database, so it may decide to re-connect to a different server
if leader-only connection is required.  It's expected that in most
cases client knows IPs of all the database servers in a cluster.

>   2.  If an ovsdb-client is connected to a follower ovsdb server, are all
>       the read/write operations forwarded to the leader by default? If not,
>       is there a way for the leader to handle all reads, writes without
>       clients knowing the leader IP.

Followers will handle monitors and read transactions by their own.
Write transactions are forwarded to a leader.
Please, read the documentation.  It covers this and a lot more:

>   3.  In ovsdb monitoring, if the client does not receive a monitoring
>       update (due to connectivity issues or if client is down), does the
>       ovsdb-server keep track of that and send it later or is it lost?

Connection is either unix socket, or TCP, or SSL.  They all guarantee
data delivery.  If connection is dropped for any reason, client will
have to establish a new connection and send a new monitor request.

> Thanking you,
> Regards,
> Rutuja Madhure
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20210726/221aaace/attachment.html>

More information about the discuss mailing list