[ovs-dev] [PATCH] ovsdb-server: drop all connections on read/write status change

Ben Pfaff blp at ovn.org
Fri Jul 12 15:21:55 UTC 2019


On Fri, Jul 12, 2019 at 03:06:34PM +0200, Daniel Alvarez Sanchez wrote:
> On Wed, Jul 10, 2019 at 10:24 PM Ben Pfaff <blp at ovn.org> wrote:
> >
> > On Tue, Jul 09, 2019 at 12:16:30PM +0200, Daniel Alvarez wrote:
> > > Prior to this patch, only db change aware connections were dropped
> > > on a read/write status change. However, current schema in OVN does
> > > not allow clients to monitor whether a particular DB changes this
> > > status. In order to accomplish this, we'd need to change the schema
> > > and adapting ovsdb-server and existing clients.
> > >
> > > Before tackling that, this patch is changing ovsdb-server to drop
> > > *all* the existing connections upon a read/write status change. This
> > > will force clients to reconnect and honor the change.
> > >
> > > Reported-at: https://mail.openvswitch.org/pipermail/ovs-discuss/2019-July/048981.html
> > > Signed-off-by: Daniel Alvarez <dalvarez at redhat.com>
> >
> > Thanks, applied to master.
> Thanks a lot Ben. Do you think it would make sense to backport it as
> far as we could get to the stable branches?

It has patch conflicts for the backport (in the test), would you mind
sending a backported version?


More information about the dev mailing list