Project

General

Profile

Bug #47720

rgw: radosgw-admin does not paginate internally when listing bucket

Added by J. Eric Ivancich 4 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Target version:
% Done:

0%

Source:
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

Currently `radosgw-admin bucket list ...`, when listing a bucket, asks
for the value of "--max-entries" internally. To list a large bucket
entirely the user would have to set "--max-entries" to a large value
(e.g., 10000000). Internally this doesn't paginate, so it will try to
produce the entire list at once. This can consume a lot of memory, and
there are known cases where this induces an out-of-memory crash.


Related issues

Copied to rgw - Backport #47818: nautilus: rgw: radosgw-admin does not paginate internally when listing bucket Resolved
Copied to rgw - Backport #47819: octopus: rgw: radosgw-admin does not paginate internally when listing bucket Resolved

History

#1 Updated by J. Eric Ivancich 4 months ago

  • Pull request ID set to 37511

#2 Updated by Nathan Cutler 4 months ago

  • Status changed from In Progress to Fix Under Review

#3 Updated by J. Eric Ivancich 4 months ago

  • Status changed from Fix Under Review to Pending Backport

#4 Updated by Nathan Cutler 3 months ago

  • Copied to Backport #47818: nautilus: rgw: radosgw-admin does not paginate internally when listing bucket added

#5 Updated by Nathan Cutler 3 months ago

  • Copied to Backport #47819: octopus: rgw: radosgw-admin does not paginate internally when listing bucket added

#6 Updated by Nathan Cutler 3 months ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF