Actions
Bug #55422
openRGW enable ops log, when max backlog reached, unable to read any data from rgw_ops_log_socket_path
% Done:
0%
Source:
Tags:
backport_processed
Backport:
quincy, pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
ceph version 16.2.7 (dd0603118f56ab514f133c8d2e3adfc983942503) pacific (stable)
1.set config option
rgw_enable_ops_log = true
rgw_ops_log_socket_path = /var/run/ceph/ceph-client.rgw.rgw-test.node1.ysyeco.unix_socket
rgw_ops_log_data_backlog = 512
2.restart rgw
3.put/get/delete objects, when the log "dropping data output, max backlog reached (skipped==0)" appears, unable to read any data from rgw_ops_log_socket_path
Updated by Radoslaw Zarzynski almost 2 years ago
- Project changed from RADOS to rgw
Updated by Matt Benjamin almost 2 years ago
- Status changed from New to Triaged
- Assignee set to Matt Benjamin
Updated by Matt Benjamin almost 2 years ago
- Status changed from Triaged to Fix Under Review
- Backport set to quincy, pacific
Updated by Casey Bodley almost 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot almost 2 years ago
- Copied to Backport #55829: quincy: RGW enable ops log, when max backlog reached, unable to read any data from rgw_ops_log_socket_path added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #55830: pacific: RGW enable ops log, when max backlog reached, unable to read any data from rgw_ops_log_socket_path added
Actions