openstack/tripleo-heat-templates
Code Issues Proposed changes

Use optimal (instead of default) tunables for Ceph on upgrade

Browse Source 
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
This commit is contained in:
Giulio Fidente 2017-07-18 11:03:35 +02:00
parent e57a7cdd73
commit 5e9f855f7c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
puppet/services/ceph-mon.yaml
View File

@ -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