Project

General

Profile

Actions
Copy link

Bug #46143

closed

osd: make message cap option usable again

Added by Neha Ojha almost 4 years ago. Updated over 3 years ago.

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

0%

Source:
Tags:
Backport:
nautilus, octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
32855
Crash signature (v1):
Crash signature (v2):

Description

"This reverts commit 45d5ac3.

Without a msg throttler, we can't change osd_client_message_cap cap
online. The throttler is designed to work with 0 as a max, so we could
change the default to 0 to disable it instead."

Related issues 2 (0 open — 2 closed)

Copied to RADOS - Backport #46164: nautilus: osd: make message cap option usable againResolvedNeha OjhaActions
Copied to RADOS - Backport #46165: octopus: osd: make message cap option usable againResolvedNeha OjhaActions
Actions
Copy link
 #1

Updated by Neha Ojha almost 4 years ago

  • Status changed from New to In Progress
  • Pull request ID set to 32855
Actions
Copy link
 #2

Updated by Neha Ojha almost 4 years ago

  • Status changed from In Progress to Fix Under Review
Actions
Copy link
 #3

Updated by Neha Ojha almost 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #4

Updated by Neha Ojha almost 4 years ago

  • Copied to Backport #46164: nautilus: osd: make message cap option usable again added
Actions
Copy link
 #5

Updated by Neha Ojha almost 4 years ago

  • Copied to Backport #46165: octopus: osd: make message cap option usable again added
Actions
Copy link
 #6

Updated by Nathan Cutler over 3 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".

Actions
Copy link

Also available in: Atom PDF