Open Stack

On Tue, Jun 14, 2016 at 9:37 AM, Sean Dague <sean at dague.net> wrote:

> On 06/14/2016 11:02 AM, Matt Riedemann wrote:
> > A question came up in the nova IRC channel this morning about the
> > api_rate_limit config option in nova which was only for the v2 API.
> >
> > Sean Dague explained that it never really worked because it was per API
> > server so if you had more than one API server it was busted. There is no
> > in-tree replacement in nova.
> >
> > So the open question here is, what are people doing as an alternative?
>
> Just as a clarification. The toy implementation that used to live in
> Nova was even worse then described above. The counters were kept per
> process. So if you had > 1 API worker (default is # of workers per CPU)
> it would be inconsistent.
>
> This is why it was defaulted in false in Havana, and never carried
> forward to the new API backend.
>
>         -Sean
>

+1 to remove that code!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160614/902e6e30/attachment.html>