]> git-server-git.apps.pok.os.sepia.ceph.com Git - ceph.git/commit
qa/suites/rados/thrash: force normal pg log length with cache tiering 28658/head
authorSage Weil <sage@redhat.com>
Wed, 19 Jun 2019 16:15:25 +0000 (11:15 -0500)
committerSage Weil <sage@redhat.com>
Wed, 19 Jun 2019 16:15:25 +0000 (11:15 -0500)
commitafd0b508c2e0f3dc529ba3a28fd180a3e8925646
treeb66498b2c44baa5e5d04d66ec51b5369a968c2ee
parent8d44d03d4d81a645e093d4f0053809107670f9b4
qa/suites/rados/thrash: force normal pg log length with cache tiering

When we are doing cache tiering, we are more sensitive to short PG logs
because the dup op entries are not perfectly promoted from the base to
the cache.

See:
 http://tracker.ceph.com/issues/38358
 http://tracker.ceph.com/issues/24320

This works around the problem by not testing short pg logs in combination
with cache tiering.  This works because the short_pg_log.yaml fragment
sets the short log in the [global] section but the cache workloads overload
it (back to a large/default value) in the [osd] section.

Signed-off-by: Sage Weil <sage@redhat.com>
qa/suites/rados/thrash/workloads/cache-agent-big.yaml
qa/suites/rados/thrash/workloads/cache-agent-small.yaml
qa/suites/rados/thrash/workloads/cache-pool-snaps-readproxy.yaml
qa/suites/rados/thrash/workloads/cache-pool-snaps.yaml
qa/suites/rados/thrash/workloads/cache-snaps.yaml
qa/suites/rados/thrash/workloads/cache.yaml