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.
talksing about this a little more on irc
this issue is in the resource tracker not the scheduled as i orgianlly thought /bugzilla. redhat. com/show_ bug.cgi? id=2283075
this is similar to https:/
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.