Bug 2110008
| Summary: | Ceph msgr should log when it reaches the DispatchQueue throttle limit | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vikhyat Umrao <vumrao> |
| Component: | RADOS | Assignee: | Brad Hubbard <bhubbard> |
| Status: | CLOSED ERRATA | QA Contact: | skanta |
| Severity: | high | Docs Contact: | Akash Raj <akraj> |
| Priority: | high | ||
| Version: | 3.1 | CC: | akraj, akupczyk, amathuri, anarnold, bhubbard, ceph-eng-bugs, cephqe-warriors, choffman, gfarnum, ksirivad, lflores, nojha, pasik, pdhange, pdhiran, pdonnell, rfriedma, rperiyas, rzarzyns, skanta, sseshasa, vereddy, vumrao |
| Target Milestone: | --- | ||
| Target Release: | 5.3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | DevNeeded | ||
| Fixed In Version: | ceph-16.2.10-22.el8cp | Doc Type: | Enhancement |
| Doc Text: |
.Low-level log messages are introduced to warn user about hitting throttle limits
Previously, there was a lack of low-level logging indication that throttle limits were hit, causing these occurrences to incorrectly have the appearance of a networking issue.
With this release, the introduction of low-level log messages makes it much clearer that the throttle limits are hit.
|
Story Points: | --- |
| Clone Of: | 1647624 | Environment: | |
| Last Closed: | 2023-01-11 17:40:00 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1647624 | ||
| Bug Blocks: | 2100747, 2126049 | ||
|
Comment 1
Vikhyat Umrao
2022-08-23 19:50:25 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Ceph Storage 5.3 security update and Bug Fix), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:0076 |