juju model-config max-history-time has no effect on juju.statuseshistory retention
Bug #1653181 reported by
Frode Nordahl
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
Juju 2.0.2 juju.statuseshi
WARNING juju.environs.
Is this setting not yet available? Does it have a different name? Warning appears on Juju 2.2 (devel) release also.
Perhaps a related symptom is "juju status" shows that many agents are lost. Restarting the API server appears to have remedied this particular problem.
tags: | added: sts |
description: | updated |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.2.0 |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju: | |
milestone: | 2.2-beta2 → 2.2-beta3 |
Changed in juju: | |
milestone: | 2.2-beta3 → 2.2-beta4 |
Changed in juju: | |
milestone: | 2.2-beta4 → 2.2-rc1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It appears pruning is going on. A count of docs in the statuseshistory that are older than a particular time did drop.
switched to db juju ory.count( {'updated' : {$lt: 148242804200000 0000}}) ory.count( {'updated' : {$lt: 148242804200000 0000}})
juju:PRIMARY> db.statuseshist
1213881
juju:PRIMARY> db.statuseshist
1213870
To further confirm, the oldest entry (minimum "updated" value) was displayed about five minutes apart, the prune interval.
juju:PRIMARY> db.statuseshist ory.aggregate( [{:{_id: null,oldest: {:''}}} ]) "14819164088131 57991") }
{ "_id" : null, "oldest" : NumberLong(
$ date -d@1481916408
Fri Dec 16 12:26:48 MST 2016
juju:PRIMARY> db.statuseshist ory.aggregate( [{:{_id: null,oldest: {:''}}} ]) "14819167123074 87461") }
{ "_id" : null, "oldest" : NumberLong(
$ date -d@1481916712
Fri Dec 16 12:31:52 MST 2016
So, it appears retention is set at two weeks (or rather 14*24*60*60*10**9; 'updated' field is in nanoseconds