Actions
Bug #42301
closedmgr/autoscaler: 1 subtrees have overcommitted pool target_size_bytes
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Health check failed: 1 subtrees have overcommitted pool target_size_bytes (POOL_TARGET_SIZE_BYTES_OVERCOMMITTED)" in cluster log
2019-10-14T07:00:18.887+0000 7fa42da5b700 10 mgr.server operator() 8 pgs: 8 active+clean; 253 GiB data, 9.3 GiB used, 110 GiB / 119 GiB avail; 7.1 MiB/s rd, 4.8 MiB/s wr, 12 op/s 2019-10-14T07:00:18.887+0000 7fa42da5b700 10 mgr.server operator() 2 health checks 2019-10-14T07:00:18.887+0000 7fa42da5b700 20 mgr.server operator() health checks: { "POOL_TARGET_SIZE_BYTES_OVERCOMMITTED": { "severity": "HEALTH_WARN", "summary": { "message": "1 subtrees have overcommitted pool target_size_bytes", "count": 1 }, "detail": [ { "message": "Pools ['rbd'] overcommit available storage by 4.240x due to target_size_bytes 0 on pools []" } ] }, "POOL_TARGET_SIZE_RATIO_OVERCOMMITTED": { "severity": "HEALTH_WARN", "summary": { "message": "1 subtrees have overcommitted pool target_size_ratio", "count": 1 }, "detail": [ { "message": "Pools ['rbd'] overcommit available storage by 4.240x due to target_size_ratio 0.000 on pools []" } ] } }
/a//kchai-2019-10-14_06:20:56-rados-wip-kefu-testing-2019-10-14-1111-distro-basic-smithi/4412618/remote/smithi142/log/ceph-mgr.x.log.gz
Updated by Sage Weil over 4 years ago
- Assignee set to Sage Weil
- Priority changed from Normal to High
Updated by Sage Weil over 4 years ago
- Status changed from New to Fix Under Review
- Backport set to nautilus
Updated by Sage Weil over 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42899: nautilus: mgr/autoscaler: 1 subtrees have overcommitted pool target_size_bytes added
Updated by Nathan Cutler over 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions