Project

General

Profile

Bug #40178

rgw/OutputDataSocket: append_output(buffer::list&) says it will (but does not) discard output at data_max_backlog

Added by Matt Benjamin over 1 year ago. Updated 11 months ago.

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

0%

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

Description

A dout message in OutputDataSocket::append_output() states that
data will be dropped when appending would cause data_max_backlog
to be exceeded--but the method appends it anyway.


Related issues

Copied to rgw - Backport #40349: nautilus: rgw/OutputDataSocket: append_output(buffer::list&) says it will (but does not) discard output at data_max_backlog Resolved
Copied to rgw - Backport #40350: luminous: rgw/OutputDataSocket: append_output(buffer::list&) says it will (but does not) discard output at data_max_backlog Resolved
Copied to rgw - Backport #40351: mimic: rgw/OutputDataSocket: append_output(buffer::list&) says it will (but does not) discard output at data_max_backlog Resolved

History

#1 Updated by Matt Benjamin over 1 year ago

  • Pull request ID set to 28415

#2 Updated by Matt Benjamin over 1 year ago

  • Status changed from In Progress to Fix Under Review

#3 Updated by Matt Benjamin over 1 year ago

  • Status changed from Fix Under Review to Pending Backport

#4 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #40349: nautilus: rgw/OutputDataSocket: append_output(buffer::list&) says it will (but does not) discard output at data_max_backlog added

#5 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #40350: luminous: rgw/OutputDataSocket: append_output(buffer::list&) says it will (but does not) discard output at data_max_backlog added

#6 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #40351: mimic: rgw/OutputDataSocket: append_output(buffer::list&) says it will (but does not) discard output at data_max_backlog added

#7 Updated by Nathan Cutler 11 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