add configuration to control the size of the "statuseshistory" collection

Bug #1681352 reported by Junien F
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Ian Booth

Bug Description

Hi,

As per https://github.com/juju/juju/blob/2.1/cmd/jujud/agent/machine.go#L1111-L1115, the retention time and maximum size of the statuseshistory collection are hardcoded.

Could we please get a configuration knob to tweak them ? 2 weeks and 5 GB is too much for our controllers, mongodb requests tending to this collection (i.e. purging old records) or simply answering requests made against it can take more that 60s to complete, which certainly doesn't help our load issues.

This is with juju 2.1.1.

Thank you !

Junien F (axino)
tags: added: canonical-is
tags: added: scalability
Revision history for this message
Junien F (axino) wrote :

This is similar to LP#1681363.

Changed in juju:
status: New → Triaged
importance: Undecided → High
importance: High → Wishlist
Changed in juju:
milestone: none → 2.2-rc1
importance: Wishlist → High
tags: added: jaas
Ian Booth (wallyworld)
Changed in juju:
milestone: 2.2-rc1 → 2.2-beta3
assignee: nobody → Ian Booth (wallyworld)
status: Triaged → In Progress
Revision history for this message
Ian Booth (wallyworld) wrote :
Revision history for this message
Anastasia (anastasia-macmood) wrote :

PR to react to config change against develop (2.2): https://github.com/juju/juju/pull/7251

Ian Booth (wallyworld)
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.