Actions
Bug #56495
closedLog at 1 when Throttle::get_or_fail() fails
% Done:
100%
Source:
Tags:
Backport:
pacific, quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When trying to debug a throttle failure we currently need to set debug_ms=20 which can delay troubleshooting due to the fact there is a tendency to try lower debugging values due to the volume of logging produced at higher levels. Therefore the following messages (and similar failure notficiations) should be generated at level 1 in my humble opinion.
2020-02-22 14:44:50.504 7fcf89f63700 10 --2- [v2:172.21.15.44:6800/32851,v1:172.21.15.44:6801/32851] >> [v2:172.21.15.44:6834/2377610774,v1:172.21.15.44:6835/2377610774] conn(0x55eea818bc00 0x55eea7be0580 crc :-1 s=THROTTLE_MESSAGE pgs=4 cs=0 l=1 rx=0 tx=0).throttle_message wants 1 message from policy throttler 128/128
Updated by Neha Ojha almost 2 years ago
- Status changed from New to Fix Under Review
Updated by Brad Hubbard almost 2 years ago
- Related to Feature #46226: msg: Messenger should log when it reaches the DispatchQueue throttle limit added
Updated by Yuri Weinstein almost 2 years ago
Updated by Brad Hubbard almost 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56641: quincy: Log at 1 when Throttle::get_or_fail() fails added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56642: pacific: Log at 1 when Throttle::get_or_fail() fails added
Updated by Konstantin Shalygin over 1 year ago
- Status changed from Pending Backport to Resolved
- % Done changed from 0 to 100
- Tags deleted (
backport_processed)
Actions