Bug 2110504

Summary:	[GSS] `The server didn't respond in time.` error is observed on accessing objects
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Sonal <sarora>
Component:	Multi-Cloud Object Gateway	Assignee:	Nimrod Becker <nbecker>
Status:	CLOSED ERRATA	QA Contact:	Mahesh Shetty <mashetty>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.8	CC:	akrai, assingh, cgaynor, dzaken, etamir, hnallurv, kbg, khover, kjosy, mashetty, mmanjuna, nbecker, ocs-bugs, odf-bz-bot, pjagtap, sbaldwin, tdesala, wburrows
Target Milestone:	---	Flags:	mashetty: needinfo- cgaynor: needinfo? (sarora) mashetty: needinfo-
Target Release:	ODF 4.12.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	4.12.0-55	Doc Type:	Bug Fix
Doc Text:	Previously, incorrect mapping of indexes in the Multicloud Object Gateway (MCG) database caused several queries to be very slow. As a result, there was a slow listing of operations on a high number of objects With this update, mapping and indexes are fixed so that the queries are optimized and listing operation is faster.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-31 00:19:40 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 Sonal 2022-07-25 13:54:09 UTC

Description of problem (please be detailed as possible and provide log
snippests):

After upgrading from OCS 4.7 to 4.8, `The server didn't respond in time.` message is observed on access a bucket with around 3 million objects


The issue is observed for some of the files/directories.

Version of all relevant components (if applicable):
OCS 4.8

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, the customer is not able to access a lot of files/directories

Is there any workaround available to the best of your knowledge?
No

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes, in customers environment

Can this issue reproduce from the UI?
Yes, using minio UI to access the data

If this is a regression, please provide more details to justify this:
Not sure

Steps to Reproduce:
1. Upgrade from OCS 4.7 to 4.8
2. Access data in large buckets having 3 million object, from mc command line and from minio UI


Actual results:
`The server didn't respond in time.` message is observed

Expected results:
The listing of objects should be successful

Additional info:
In the next private comment

Comment 4 khover 2022-07-25 17:43:18 UTC

DB

                        "resources": {
                            "limits": {
                                "cpu": "500m",
                                "memory": "500Mi"
                            },
                            "requests": {
                                "cpu": "500m",
                                "memory": "500Mi"

Endpoint

                        "resources": {
                            "limits": {
                                "cpu": "1",
                                "memory": "2Gi"
                            },
                            "requests": {
                                "cpu": "1",
                                "memory": "2Gi"

Comment 17 Nimrod Becker 2022-09-08 11:56:28 UTC

Changing product from OCS to ODF so we can update flags

Comment 57 Nimrod Becker 2023-01-30 17:38:04 UTC

ack

Comment 59 errata-xmlrpc 2023-01-31 00:19:40 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenShift Data Foundation 4.12.0 enhancement and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:0551