lease Manager should not evaluate all Leases and all Blocks on every loop()
Bug #1814556 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
| 2.5 |
Fix Released
|
High
|
John A Meinel | ||
Bug Description
worker/
Once in nextTick() to figure out when the next tick would be and once in loop() where it checks if there are any blocks to unblock.
However, we should only need to unblock if something expired, and we can compute nextTick once when we evaluate the leases, and then only tick the clock forward a bit if a ClaimLease would cause the most-recent expiry to be newer than the previous most recent.
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in juju: | |
| assignee: | nobody → Christian Muirhead (2-xtian) |
| milestone: | none → 2.6-beta1 |
| Changed in juju: | |
| assignee: | Christian Muirhead (2-xtian) → John A Meinel (jameinel) |
Revision history for this message
| John A Meinel (jameinel) wrote | #2 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/