yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #94074
[Bug 2068893] Re: 414 Request-Too-Long when using _get_sharing_providers with a large number of UUIDs
talksing about this a little more on irc
this issue is in the resource tracker not the scheduled as i orgianlly thought
this is similar to https://bugzilla.redhat.com/show_bug.cgi?id=2283075
currently the resource tracker is caching the set of sharing agggates it
is a part of.
in some cases this is very large and can hit limits in the loadblancer
or webserver.
sahid's proposal is to paginate the request which may be valided.
currently its not clear that the cached data in the resouce tracker is
actually required and as such removal of this cached data might also be
an option.
setting this to medium as the work around for now is to increase the max
request size on the webserver or loadbalnacer.
the current limit is deployment tool specififc.
** Tags added: resource-tracker
** Bug watch added: Red Hat Bugzilla #2283075
https://bugzilla.redhat.com/show_bug.cgi?id=2283075
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova
Status: Opinion => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2068893
Title:
414 Request-Too-Long when using _get_sharing_providers with a large
number of UUIDs
Status in OpenStack Compute (nova):
Triaged
Bug description:
The scheduler is reporting error when calling placement in situation
of hosts running into many aggregates
The web server returns a 414 Request-Too-Long error because the size
of the URL in the GET request exceeds the allowed limit.
The proposed fix is some modifications in _get_sharing_providers
function to divide the agg_uuids list into groups of a maximum of 100
UUIDs per GET request. The division ensures that the size of each
request remains below the allowed limit, resolving the issue of the
414 Request-Too-Long error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2068893/+subscriptions
References