Bug 1425115 - MON - OSD communication, OSDs are not marked down when co-located with MONs
Summary: MON - OSD communication, OSDs are not marked down when co-located with MONs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 2.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 2.3
Assignee: Kefu Chai
QA Contact: Vidushi Mishra
Erin Donnelly
URL:
Whiteboard:
Depends On:
Blocks: 1437916
TreeView+ depends on / blocked
 
Reported: 2017-02-20 15:25 UTC by Tomas Petr
Modified: 2020-03-11 15:49 UTC (History)
9 users (show)

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.
Clone Of:
Environment:
Last Closed: 2017-06-19 13:29:50 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 18104 0 None None None 2017-02-23 11:28:55 UTC
Red Hat Knowledge Base (Solution) 2937431 0 None None None 2017-02-27 13:49:36 UTC
Red Hat Product Errata RHBA-2017:1497 0 normal SHIPPED_LIVE Red Hat Ceph Storage 2.3 bug fix and enhancement update 2017-06-19 17:24:11 UTC

Description Tomas Petr 2017-02-20 15:25:06 UTC 
Description of problem:
MON - OSD communication, OSDs are not marked down when co-located with MONs:
In the RHCS 2.1 co-located environment MONs and OSDs, if the co-located node is shuted down, the osds are NOT marked as down. The terminated monitor leaves quorum correctly. 
If is is during HW outage and the noout flag is set, the osds stay marked as "up" forever. If we manually perform "ceph osd down X", after 15 minutes f.e., all osds from this node are recognized as down.
If the noout flag is not set, the osds are marked as down and out after 300s.
Nodes that are pure ODS only are marked down correctly every time. 

Version-Release number of selected component (if applicable):
ceph version 10.2.3-17.el7cp

How reproducible:
Every time

Steps to Reproduce:
1. create  co-located RHCS 2 
2. shutdown one co-located node
3. osds are not recognized as down

Actual results:
osds are not recognized as down

Expected results:
osds are recognized as down

Additional info:
on RHCS 1.3 works fine
Comment 2 Vikhyat Umrao 2017-02-20 15:33:46 UTC 
Tested in RHCS 1.3.3(0.94.9-8.el7cp) all works fine. Added 'regression' keyword.
Comment 11 Shinobu KINJO 2017-02-21 03:26:25 UTC 
Under collocation both MONs and OSDs situation,
Comment 22 Vikhyat Umrao 2017-02-23 15:54:30 UTC 
jewel backport tracker: http://tracker.ceph.com/issues/18104
jewel backport patch: https://github.com/ceph/ceph/pull/12677/commits/dcc9483cbd605997876983ec65f6fb80d5da8a52
Comment 23 Josh Durgin 2017-04-01 01:33:39 UTC 
Included in upstream 10.2.6.
Comment 33 errata-xmlrpc 2017-06-19 13:29:50 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, 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
Note You need to log in before you can comment on or make changes to this bug.