Not very frequent, may be a few times per day per participating device. However, if DB is reasonably big and there are many monitoring clients, it might get busy as clients reread all the data to find what changed since monitors were dropped. Can also make the troubleshooting more tricky as loss of connectivity doesn't mean failure and there is no clear indication on the reason of disconnection.
I understand that it might not be a priority for you - would it be possible for us to contribute in order to enhance this aspect? Thanks, Michael -----Original Message----- From: Ben Pfaff [mailto:b...@nicira.com] Sent: Tuesday, November 11, 2014 2:03 PM To: Zayats, Michael Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] OVSDB list_dbs monitor/update On Tue, Nov 11, 2014 at 09:57:21PM +0000, Zayats, Michael wrote: > OVSDB protocol has the means to retrieve a list of databases being managed by > the server. > However, the list might change, using for example add-db/remove-db runtime > management command of ovsdb-server. > > Would it make sense to add a monitor/update capabilities for the db listing? > Current protocol seems to force periodic polling, with quite a few > undesirable side effects on other interactions with the server. Currently, ovsdb-server drops all connections whenever a database is added or removed, so each client can simply check the list when it reconnects. Unless databases are frequently added or removed (do you plan to do that?) I doubt that it is a big deal. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
