Bug 1425115
Summary: | MON - OSD communication, OSDs are not marked down when co-located with MONs | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Tomas Petr <tpetr> |
Component: | RADOS | Assignee: | Kefu Chai <kchai> |
Status: | CLOSED ERRATA | QA Contact: | Vidushi Mishra <vimishra> |
Severity: | high | Docs Contact: | Erin Donnelly <edonnell> |
Priority: | high | ||
Version: | 2.1 | CC: | ceph-eng-bugs, dzafman, edonnell, hnallurv, jdurgin, kchai, kdreyer, skinjo, vumrao |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | 2.3 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-10.2.7-2.el7cp Ubuntu: ceph_10.2.7-3redhat1xenial | Doc Type: | Bug Fix |
Doc Text: |
.An OSD failure no longer causes significant delay
Previously, when an OSD and a Monitor were colocated on the same node and the node failed, Ceph waited some time before sending the note to the Monitor so the Monitor could decide if it wanted to mark the OSD as down. This could lead to a significant delay. With this update, when an OSD is known to be down, the cluster becomes aware immediately after the failure report, and Ceph sends the note to the Monitor right away.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-19 13:29:50 UTC | Type: | Bug |
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: | |||
Bug Blocks: | 1437916 |
Description
Tomas Petr
2017-02-20 15:25:06 UTC
Tested in RHCS 1.3.3(0.94.9-8.el7cp) all works fine. Added 'regression' keyword. Under collocation both MONs and OSDs situation, jewel backport tracker: http://tracker.ceph.com/issues/18104 jewel backport patch: https://github.com/ceph/ceph/pull/12677/commits/dcc9483cbd605997876983ec65f6fb80d5da8a52 Included in upstream 10.2.6. 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, 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/RHBA-2017:1497 |