status sitory pruner needs to remove only once
Bug #1577593 reported by
Horacio Durán
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Low
|
Unassigned | ||
Bug Description
StatusHistoryPruner worker removes old status history entries trying to keep either N time of backlog or N MBytes of logs whatever is smaller, currently it deletes the time backlog and then, if the size is still over the passed limit it deletes logs until the size is reached.
Ideally it should check size and backlog first and then delete once to avoid hitting twice the db.
The expected workflow:
* validate request sanity
* figure out oldest record to keep
* (try both, take most recent result)
* remove all older records
| Changed in juju-core: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| milestone: | none → 2.0.1 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0.1 → none |
| milestone: | none → 2.0.1 |
| Changed in juju: | |
| milestone: | 2.0.1 → none |
| Changed in juju: | |
| importance: | Medium → Low |
| assignee: | Horacio Durán (hduran-8) → nobody |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.