Bug 2281592
Summary: | rbd-mirror daemon in ERROR state, require manual restart [5.3z] | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Ilya Dryomov <idryomov> |
Component: | RBD-Mirror | Assignee: | Ilya Dryomov <idryomov> |
Status: | CLOSED ERRATA | QA Contact: | Sunil Angadi <sangadi> |
Severity: | high | Docs Contact: | Disha Walvekar <dwalveka> |
Priority: | unspecified | ||
Version: | 5.3 | CC: | asriram, ceph-eng-bugs, cephqe-warriors, dwalveka, sangadi, tserlin |
Target Milestone: | --- | ||
Target Release: | 5.3z7 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-16.2.10-258.el8cp | Doc Type: | Bug Fix |
Doc Text: |
Previously, due to an implementation defect, `rbd-mirror` daemon did not properly dispose of outdated `PoolReplayer` instances in particular when refreshing the mirror peer configuration.
Due to this there was unnecessary resource consumption and number of `PoolReplayer` instances competed with each other causing `rbd-mirror` daemon health to be reported as ERROR and replication would hang in some cases. To resume replication the administrator had to restart the `rbd-mirror` daemon.
With this fix, the implementation defect is corrected and rbd-mirror daemon now properly disposes of outdated `PoolReplayer` instances.
|
Story Points: | --- |
Clone Of: | 2279528 | Environment: | |
Last Closed: | 2024-06-26 10:02:43 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: |
Comment 5
Sunil Angadi
2024-06-04 12:49:43 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, bug fix, and enhancement update), 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-2024:4118 |