Bug #8043
closed
- Source changed from other to Development
Is the concern the need for scrub, or are there other issues?
We could make the (shallow) scrub triggered automatically when the agent sees the invalid_stats flag. Or, we could make the mon refuse to split unless provided a --force flag...
Requiring a scrub first means that any cache pool which is actually being used and gets split will fill up and block IO (because it will be running nearly full to begin with) before the scrub completes.
How about a flag in the pg info that prevents the agent from blocking on full until it sees the thresholds drop below the target?
Do you really expect cache pool targets to not be set based on the underlying storage capacity? (Hint: no.)
;)
- Status changed from New to Fix Under Review
- Status changed from Fix Under Review to Resolved
Also available in: Atom
PDF