Bug #44772
RGW tries to cache and access anonymous user
% Done:
0%
Source:
Development
Tags:
Backport:
octopus, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
When object have public-read permissions and the user is unauthenticated (for example repo), The RGW will try anyway to access metadata of anonymous user (that is not exist ofcourse) and try to cache it for every request (every request gets cache miss), As a result the latency for those requests is unnecessarily higher and there are necessarily RADOS ops.
Related issues
History
#1 Updated by Casey Bodley about 4 years ago
- Status changed from New to Triaged
- Assignee set to Or Friedmann
#2 Updated by Casey Bodley almost 4 years ago
- Status changed from Triaged to Fix Under Review
- Pull request ID set to 34287
#3 Updated by Casey Bodley almost 4 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to octopus
#4 Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #45484: octopus: RGW tries to cache and access anonymous user added
#5 Updated by Nathan Cutler almost 4 years 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".
#6 Updated by Ken Dreyer almost 4 years ago
- Backport changed from octopus to octopus, nautilus