Code Review / apex-tripleo-heat-templates.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: e57a7cd) | patch
Use optimal (instead of default) tunables for Ceph on upgrade
authorGiulio Fidente <gfidente@redhat.com>
Tue, 18 Jul 2017 09:03:35 +0000 (11:03 +0200)
committerGiulio Fidente <gfidente@redhat.com>
Tue, 18 Jul 2017 09:03:35 +0000 (11:03 +0200)
commit5e9f855f7c96950ca29a0f85086441c57ae7aed5
tree493ca1d692660deefc6a9cad3a250ec1e1bc43f8tree | snapshot
parente57a7cdd733c5edd974749cd21e0563c8c6ca9facommit | diff
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 diff | blob | history