Change zk logging configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
Critical
|
Kapil Thangavelu | ||
juju (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Precise |
Fix Released
|
Critical
|
Unassigned |
Bug Description
== SRU Justifcation ==
=== Impact ===
This bug can cause juju's local provider to fill up the local disk very rapidly after a reboot.
=== Test Case ===
1. Create a local environment in ~/.juju/
environments:
local:
type: local
data-dir: /home/myuser/
default-series: precise
2. juju bootstrap
3. reboot the machine
4. check /home/myuser/
5. juju destroy-environment
6. update the package
7. repeat steps 1 - 4. If the logs are no longer streaming, the bug is fixed.
=== Dev Fix ===
This is fixed in upstream commit 533 by suppressing the logs from libzookeeper.
=== Regression Potential ===
Very low, this simply suppresses the logs that come streaming out of libzookeeper, and they are not useful in most cases. This does mean that in the rare cases where client error logs would be useful, they are suppressed.
== Original Bug Description ==
The verbosity and frequency of the zookeeper log is considerable, use a pipe and filter on level and rate. Lacking this its possible for the log to fill up the disks on the machine for a disconnected agent, happeneRd to me on local provider, ugh. Just to be clear this on the client connection logging, not the server.
Related branches
- Juju Engineering: Pending requested
-
Diff: 11 lines (+1/-0)1 file modifiedjuju/agents/base.py (+1/-0)
description: | updated |
Changed in juju: | |
milestone: | none → florence |
importance: | Undecided → High |
description: | updated |
Changed in juju: | |
assignee: | nobody → Kapil Thangavelu (hazmat) |
status: | New → In Progress |
Changed in juju: | |
status: | In Progress → Fix Released |
Changed in juju: | |
importance: | Medium → Critical |
description: | updated |
Changed in juju (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in juju (Ubuntu Precise): | |
milestone: | none → ubuntu-12.04.1 |
the switch to managed zk client mitigates this significantly as typicaly it was the error stream from an expired session that cause the problem.