Bug 1489063 - backport: increase min_in_ratio to .75 (from .3)
Summary: backport: increase min_in_ratio to .75 (from .3)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 2.4
Hardware: All
OS: All
unspecified
high
Target Milestone: rc
: 2.5
Assignee: Josh Durgin
QA Contact: Manohar Murthy
Bara Ancincova
URL:
Whiteboard:
Depends On:
Blocks: 1536401
TreeView+ depends on / blocked
 
Reported: 2017-09-06 15:57 UTC by Sage Weil
Modified: 2020-12-14 09:54 UTC (History)
8 users (show)

Fixed In Version: RHEL: ceph-10.2.10-1.el7cp Ubuntu: ceph_10.2.10-2redhat1xenial
Doc Type: Enhancement
Doc Text:
.The default value for the `min_in_ratio` option has been increased to `0.75` The `min_in_ratio` option prevents Monitors from marking OSDs as `out` when the amount of `out` OSDs drops below certain fraction of all OSDs in the cluster. In previous releases, the default value of `min_in_ratio` was set to `0.3`. With this update, the value has been increased to `0.75`.
Clone Of:
Environment:
Last Closed: 2018-02-21 19:43:32 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph pull 15050 0 None None None 2017-09-06 16:17:09 UTC
Red Hat Product Errata RHBA-2018:0340 0 normal SHIPPED_LIVE Red Hat Ceph Storage 2.5 bug fix and enhancement update 2018-02-22 00:50:32 UTC

Description Sage Weil 2017-09-06 15:57:00 UTC 
Description of problem:

The min in ratio prevents the mon from marking OSDs out once we drop below some fraction of the total OSDs in the system.  This prevents too many PGs from piling up on the surviving osds.  This was .3 in hammer and jewel.  In luminous we increased in to .75.

That increase has been backported to upstream jewel in 0412bf2adaf07e527ac6659c9bce0d406edeca93.

Make sure that patch in included in the next downstream 2.y release.
Comment 3 Ken Dreyer (Red Hat) 2018-01-02 21:25:59 UTC 
Fix is in Ceph v10.2.10 upstream
Comment 10 errata-xmlrpc 2018-02-21 19:43:32 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-2018:0340
Note You need to log in before you can comment on or make changes to this bug.