Permalink
Browse files

Merge pull request #12408 from badone/wip-mon_osd_down_out_interval-d…

…ocfix

doc: Modify documentation for mon_osd_down_out_interval

Reviewed-by: xiexingguo <xie.xingguo@zte.com.cn>
  • Loading branch information...
2 parents 21c0c59 + e793376 commit 483969fcc64902db3ec24cedfcc4f207ff8eebda @badone badone committed on GitHub Dec 9, 2016
@@ -286,7 +286,7 @@ Monitor Settings
``down`` and ``out`` if it doesn't respond.
:Type: 32-bit Integer
-:Default: ``300``
+:Default: ``600``
``mon osd down out subtree limit``
@@ -439,7 +439,7 @@ still write a new object to a ``degraded`` placement group if it is ``active``.
If an OSD is ``down`` and the ``degraded`` condition persists, Ceph may mark the
``down`` OSD as ``out`` of the cluster and remap the data from the ``down`` OSD
to another OSD. The time between being marked ``down`` and being marked ``out``
-is controlled by ``mon osd down out interval``, which is set to ``300`` seconds
+is controlled by ``mon osd down out interval``, which is set to ``600`` seconds
by default.
A placement group can also be ``degraded``, because Ceph cannot find one or more
@@ -23,7 +23,7 @@
mon data = /data/mondata/mon$num
debug mon = 20
debug ms = 20
- mon osd down out interval = 0 ; 10 minutes
+ mon osd down out interval = 600 ; 10 minutes
[mon0]
host = cosd0
@@ -207,8 +207,8 @@
# The number of seconds Ceph waits before marking a Ceph OSD
# Daemon "down" and "out" if it doesn't respond.
# Type: 32-bit Integer
- # (Default: 300)
- ;mon osd down out interval = 300
+ # (Default: 600)
+ ;mon osd down out interval = 600
# The grace period in seconds before declaring unresponsive Ceph OSD
# Daemons "down".

0 comments on commit 483969f

Please sign in to comment.