Bug 1662938

Summary:	502 server error when querying for a lot of bug IDs via Bug.search
Product:	[Community] Bugzilla	Reporter:	Ales Zelinka <azelinka>
Component:	Performance	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED NOTABUG	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	azelinka, khong, qgong
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-03 06:36:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ales Zelinka 2019-01-02 13:20:21 UTC

Description of problem:
query xml-rpc Bug.search with 3500+ bug ids. Request dies with 502 server error.

This might simply be a case of too many individual bugs in one query but Bugzilla v4 used to handle such queries well so I'm filing it

Version-Release number of selected component (if applicable):
5.0.4.rh11

How reproducible:
always

Steps to Reproduce:
1. search for a list of 3500 individual bugzilla IDs

Comment 1 Jeff Fearn 🐞 2019-01-13 23:33:06 UTC

Are you specifying the fields you want? If not then it's probably caused by Bug 1658176

Comment 2 Jeff Fearn 🐞 2019-02-28 05:05:57 UTC

Can you test this again? Bug 1658176 should have made these requests a lot lighter.

FYI the 502 isn't the request dying, it's the proxy terminating the connection to the client. The request will actually complete but the results are lost.

Comment 3 Jeff Fearn 🐞 2019-06-03 06:36:18 UTC

I'm going to assume that this was caused by Bug 1658176 , if you can still duplicate it feel free to reopen this bug with the details.