[ovs-dev] [PATCH] jsonrpc: Warn about excessive sending backlog.

[Ben Pfaff]

Ah, great.  I don't think of that as "rate limiting", hence my
confusion.

I'll review the series.

Thank you!

On Thu, Sep 18, 2014 at 04:04:18PM -0700, Alex Wang wrote:
> Hey Ben,
> 
> I sent out a new series of patches here:
> http://openvswitch.org/pipermail/dev/2014-September/045949.html
> which does exactly what you said.
> 
> Forgot to mark this thread as invalid.
> 
> Thanks,
> Alex Wang,
> 
> On Thu, Sep 18, 2014 at 4:00 PM, Ben Pfaff <blp at nicira.com> wrote:
> 
> > On Thu, Sep 18, 2014 at 11:37:08AM -0700, Alex Wang wrote:
> > > When ovs is running with large topology (e.g. large number of
> > > interfaces), the stats and status update to ovsdb become huge and
> > > normally require multiple run of ovsdb jsonrpc message processing
> > > loop to consume.  Also, this could cause jsonrpc messages backlogged
> > > in ovs.
> > >
> > > This commit adds a warning message to warn the excessive backlog
> > > for jsonrpc.
> > >
> > > Signed-off-by: Alex Wang <alexw at nicira.com>
> >
> > Is this the correct way to do it?  I would have thought that as long as
> > there are any backlogged stats messages, ovs-vswitchd should defer
> > sending any further stats updates until the backlog clears.
> >