Project

General

Profile

Feature #46226

msg: Messenger should log when it reaches the DispatchQueue throttle limit

Added by Jos Collin over 2 years ago. Updated 5 months ago.

Status:
Fix Under Review
Priority:
Normal
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
pacific,octopus,nautilus
Reviewed:
Affected Versions:
Pull request ID:

Description

Right now there is no low debug output indicating that the throttle is reached which, in production, can give the appearance of network issues. In particular, hitting the DispatchQueue::dispatch_throttler limit will even prevent fast dispatch of critical messages. There should be a message whenever we hit the limit and a debug message has not been output recently (30 seconds?).


Related issues

Related to RADOS - Bug #56495: Log at 1 when Throttle::get_or_fail() fails Resolved

History

#1 Updated by Patrick Donnelly over 2 years ago

  • Project changed from CephFS to Ceph
  • Category deleted (Correctness/Safety)
  • Status changed from New to In Progress
  • Assignee set to Jos Collin
  • Target version set to v16.0.0
  • Backport set to octopus,nautilus

#2 Updated by Patrick Donnelly over 2 years ago

  • Project changed from Ceph to Messengers

#3 Updated by Jos Collin over 2 years ago

  • Pull request ID set to 36135

#4 Updated by Jos Collin about 2 years ago

  • Pull request ID changed from 36135 to 37954

#5 Updated by Jos Collin about 2 years ago

  • Status changed from In Progress to Fix Under Review

#6 Updated by Jos Collin almost 2 years ago

  • Status changed from Fix Under Review to Pending Backport

#9 Updated by Jos Collin almost 2 years ago

  • Backport changed from octopus,nautilus to pacific,octopus,nautilus

#11 Updated by Jos Collin almost 2 years ago

  • Status changed from Pending Backport to In Progress

#12 Updated by Jos Collin almost 2 years ago

  • Pull request ID deleted (37954)

#13 Updated by Jos Collin almost 2 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 39510

#14 Updated by Nathan Cutler over 1 year ago

I deleted the prematurely opened backport issues because they were showing up in the backport listings and creating confusion for backporters.

Once the master PR gets merged, the Backport Bot will open new backport issues, so nothing is lost.

#15 Updated by Brad Hubbard 5 months ago

https://tracker.ceph.com/issues/56495 is a quick and at least partial fix for this.

#16 Updated by Brad Hubbard 5 months ago

  • Related to Bug #56495: Log at 1 when Throttle::get_or_fail() fails added

Also available in: Atom PDF