From 5e9f855f7c96950ca29a0f85086441c57ae7aed5 Mon Sep 17 00:00:00 2001 From: Giulio Fidente Date: Tue, 18 Jul 2017 11:03:35 +0200 Subject: Use optimal (instead of default) tunables for Ceph on upgrade With the default setting, after the majority of the monitors have been upgraded the cluster will go in WARN state because of legacy tunables. This changes the tunables we set after each monitor is upgraded from 'default' to 'optimal' [1]. 1. http://docs.ceph.com/docs/master/rados/operations/crush-map/#warning-when-tunables-are-non-optimal Change-Id: I0f16c29cc200d762f0c4acfd87ba7d1adb5c1eeb Closes-Bug: #1704959 --- puppet/services/ceph-mon.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'puppet/services') diff --git a/puppet/services/ceph-mon.yaml b/puppet/services/ceph-mon.yaml index 4fe6e908..3e4f5b42 100644 --- a/puppet/services/ceph-mon.yaml +++ b/puppet/services/ceph-mon.yaml @@ -172,6 +172,6 @@ outputs: until: ceph_quorum_nodecheck.rc == 0 retries: {get_param: CephValidationRetries} delay: {get_param: CephValidationDelay} - - name: ceph osd crush tunables default + - name: set crush tunables tags: step0 - shell: ceph osd crush tunables default + shell: ceph osd crush tunables optimal -- cgit 1.2.3-korg