SetTools fills up transaction log

Bug #1454059 reported by John A Meinel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Medium
Unassigned

Bug Description

Associated with https://bugs.launchpad.net/juju-core/+bug/1454043 the other thing that is filling up the TXN queue is calls $set: {"tools"}.
This may just be a case of "agents are bouncing a lot" and everytime they bounce they set their tools. And in a stable system we wouldn't be bouncing as much.

It does bring up the question if a call to SetToolsVersion is a no-op should we be creating a transaction? I don't think we are worried about concurrent updates, as there should only be 1 agent trying to set its version at any given time.
I suppose if we miss the version then we may not notice that we should be upgrading our version. It is possible to get out of this situation by bouncing an agent (restart jujud-machine-X) at any point.

This gives evidence that it might be really good to do so.

Ante Karamatić (ivoks)
tags: added: cpec
Curtis Hovey (sinzui)
Changed in juju-core:
importance: High → Medium
Changed in juju-core:
milestone: none → 2.1.0
affects: juju-core → juju
Changed in juju:
milestone: 2.1.0 → none
milestone: none → 2.1.0
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.1-rc2 → none
Ante Karamatić (ivoks)
tags: added: cpe-onsite
removed: cpec
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

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.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
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.