Bug 2110504 - [GSS] `The server didn't respond in time.` error is observed on accessing objects
Summary: [GSS] `The server didn't respond in time.` error is observed on accessing obj...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.8
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: ODF 4.12.0
Assignee: Nimrod Becker
QA Contact: Mahesh Shetty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-25 13:54 UTC by Sonal
Modified: 2023-12-08 04:29 UTC (History)
18 users (show)

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.
Clone Of:
Environment:
Last Closed: 2023-01-31 00:19:40 UTC
Embargoed:
mashetty: needinfo-
mashetty: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github noobaa noobaa-core pull 7040 0 None Merged Fixed map_common_prefixes queries 2022-09-08 11:05:05 UTC
Github red-hat-storage ocs-ci pull 6499 0 None Merged Bug 2110504 List large number of objects with prefix and delimeter 2023-02-10 07:43:41 UTC
Red Hat Product Errata RHBA-2023:0551 0 None None None 2023-01-31 00:19:59 UTC

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

Comment 60 Red Hat Bugzilla 2023-12-08 04:29:47 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.