mirror of
https://github.com/ceph/ceph
synced 2026-08-02 07:03:18 +00:00
252d149238
Introduce a 'last_degraded' timestamp to the pg_stat_t structure to track
the initial point of redundancy loss. This field, used in conjunction
with 'last_clean', allows the manager to calculate a cluster-wide
durability score by measuring the duration of vulnerability windows.
Changes:
1) Add last_degraded (utime_t) to pg_stat_t in osd_types.h.
2) Increment pg_stat_t encoding version to 31. The decode logic
defaults last_degraded to last_clean for backward compatibility
during rolling upgrades.
3) Update operator==, dump(), and generate_test_instances() to
support ceph-dencoder testing and JSON output.
4) Implement latching logic in PeeringState::prepare_stats_for_publish():
- A PG is considered vulnerable if in DEGRADED or UNDERSIZED state.
- last_degraded is set to 'now' only if it is <= last_clean,
effectively latching the timestamp to the start of the failure
event until the PG next becomes clean.
5) Standalone tests to verify:
- The last_degraded timestamp latching logic.
- Verify last_degraded timestamp is modified when OSDs are marked 'out' for
draining purposes in which case PGs are marked undersized.
6) Release note the addition of 'last_degraded' field to PG stats.
Fixes: https://tracker.ceph.com/issues/76604
Signed-off-by: Sridhar Seshasayee <sridhar.seshasayee@ibm.com>
|
||
|---|---|---|
| .. | ||
| archs | ||
| cephfs | ||
| client | ||
| clusters | ||
| config | ||
| crontab | ||
| debug | ||
| distros | ||
| erasure-code | ||
| libceph | ||
| machine_types | ||
| mds | ||
| mon/bootstrap | ||
| mon_election | ||
| msgr | ||
| nightlies | ||
| objectstore | ||
| objectstore_cephfs | ||
| objectstore_crimson | ||
| objectstore_debug | ||
| overrides | ||
| packages | ||
| rbd | ||
| releases | ||
| rgw | ||
| rgw_bucket_sharding | ||
| rgw_frontend | ||
| rgw_pool_type | ||
| standalone | ||
| suites | ||
| tasks | ||
| timezone | ||
| workunits | ||
| .gitignore | ||
| .qa | ||
| asan.supp | ||
| CMakeLists.txt | ||
| find-used-ports.sh | ||
| loopall.sh | ||
| lsan.supp | ||
| Makefile | ||
| mypy.ini | ||
| README | ||
| run_xfstests_qemu.sh | ||
| run_xfstests-obsolete.sh | ||
| run_xfstests.sh | ||
| run-standalone.sh | ||
| runallonce.sh | ||
| runoncfuse.sh | ||
| runonkclient.sh | ||
| setup-chroot.sh | ||
| test_import.py | ||
| tox.ini | ||
| valgrind.supp | ||
ceph-qa-suite ------------- clusters/ - some predefined cluster layouts suites/ - set suite The suites directory has a hierarchical collection of tests. This can be freeform, but generally follows the convention of suites/<test suite name>/<test group>/... A test is described by a yaml fragment. A test can exist as a single .yaml file in the directory tree. For example: suites/foo/one.yaml suites/foo/two.yaml is a simple group of two tests. A directory with a magic '+' file represents a test that combines all other items in the directory into a single yaml fragment. For example: suites/foo/bar/+ suites/foo/bar/a.yaml suites/foo/bar/b.yaml suites/foo/bar/c.yaml is a single test consisting of a + b + c. A directory with a magic '%' file represents a test matrix formed from all other items in the directory. For example, suites/baz/% suites/baz/a.yaml suites/baz/b/b1.yaml suites/baz/b/b2.yaml suites/baz/c.yaml suites/baz/d/d1.yaml suites/baz/d/d2.yaml is a 4-dimensional test matrix. Two dimensions (a, c) are trivial (1 item), so this is really 2x2 = 4 tests, which are a + b1 + c + d1 a + b1 + c + d2 a + b2 + c + d1 a + b2 + c + d2 A directory with a magic '$' file, or a directory whose name ends with '$', represents a test where one of the non-magic items is chosen randomly. For example, both suites/foo/$ suites/foo/a.yaml suites/foo/b.yaml suites/foo/c.yaml and suites/foo$/a.yaml suites/foo$/b.yaml suites/foo$/c.yaml is a single test, either a, b or c. This can be used in conjunction with the '%' file in the same (see below) or other directories to run a series of tests without causing an unwanted increase in the total number of jobs run. Symlinks are okay. One particular use of symlinks is to combine '%' and the latter form of '$' feature. Consider supported_distros directory containing fragments that define os_type and os_version: supported_distros/% supported_distros/centos.yaml supported_distros/rhel.yaml supported_distros/ubuntu.yaml A test that links supported_distros as distros (a name that doesn't end with '$') will be run three times: on centos, rhel and ubuntu. A test that links supported_distros as distros$ will be run just once: either on centos, rhel or ubuntu, chosen randomly. The teuthology code can be found in https://github.com/ceph/teuthology.git Note: The performance suites clone CBT from master here: https://github.com/ceph/cbt.git CBT will not support cosbench beyond release tag v0.3, therefore no qa suite should use cosbench. cosbench support has been removed from qa/tasks/cbt.py.
