Feature #46226
open
msg: Messenger should log when it reaches the DispatchQueue throttle limit
Added by Jos Collin almost 4 years ago.
Updated almost 2 years ago.
Backport:
pacific,octopus,nautilus
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?).
- 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
- Project changed from Ceph to Messengers
- Pull request ID set to 36135
- Pull request ID changed from 36135 to 37954
- Status changed from In Progress to Fix Under Review
- Status changed from Fix Under Review to Pending Backport
- Backport changed from octopus,nautilus to pacific,octopus,nautilus
- Status changed from Pending Backport to In Progress
- Pull request ID deleted (
37954)
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 39510
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.
- Related to Bug #56495: Log at 1 when Throttle::get_or_fail() fails added
Also available in: Atom
PDF