From 355b652ed407f07d951b70d7797dde38f81f97bd Mon Sep 17 00:00:00 2001 From: Louis Date: Tue, 23 Apr 2019 11:23:37 +0800 Subject: [PATCH] update ROOK_MON_HEALTHCHECK_INTERVAL Signed-off-by: Louis --- design/mon-health.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/design/mon-health.md b/design/mon-health.md index 1fedf5fbf..c52808ca0 100644 --- a/design/mon-health.md +++ b/design/mon-health.md @@ -48,7 +48,7 @@ to be re-created. Without this host path, the mon cannot start again. If the mitigating steps for mon failure don't bring a mon back up, the operator will make the decision to terminate the old monitor pod and bring up a new monitor with a new identity. This is an operation that must be done while there is mon quorum. -The operator checks for mon health every 20 seconds. If a monitor is down, the operator will wait 5 minutes before failing over the bad mon. +The operator checks for mon health every 45 seconds. If a monitor is down, the operator will wait 5 minutes before failing over the bad mon. These two intervals can be configured as parameters to the rook [operator pod](/cluster/examples/kubernetes/ceph/operator.yaml). If the intervals are too short, it could be unhealthy if the mons are failed over too aggressively. If the intervals are too long, the cluster could be at risk of losing quorum if a new monitor is not brought up before another mon fails. ``` - name: ROOK_MON_HEALTHCHECK_INTERVAL