Juju state server database is overly large
Bug #1344940 reported by
Mark Shuttleworth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
1.20 |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
On a machine which is being used to build out an openstack:
ubuntu@pbdpm:~$ sudo du -csh /var/lib/juju/
51G /var/lib/juju/
51G total
Is there any reason to pre-allocate that much space?
tags: | added: canonical-is |
tags: | added: cloud-installer landscape |
tags: | added: mongodb |
Changed in juju-core: | |
assignee: | nobody → Andrew Wilkins (axwalk) |
milestone: | 1.20.2 → 1.21-alpha1 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
the problem is 1000s of writes without an actual change, ie. the transaction log is full of these
stateServer s:apiHostPorts update {u'$set': {u'apihostports': [[{u'networkscope': u'public', u'addresstype': u'hostname', u'port': 17070, u'value': u'pbdpm. cluster. mallards' }, {u'networkscope': u'local-cloud',\ :225:90ff: fe4c:e79e' }]]}} s:apiHostPorts update {u'$set': {u'apihostports': [[{u'networkscope': u'public', u'addresstype': u'hostname', u'port': 17070, u'value': u'pbdpm. cluster. mallards' }, {u'networkscope': u'local-cloud',\ :225:90ff: fe4c:e79e' }]]}}
u'addresstype': u'ipv4', u'port': 17070, u'value': u'192.168.9.74'}, {u'networkscope': u'local-machine', u'addresstype': u'ipv4', u'port': 17070, u'value': u'127.0.0.1'}, {u'networkscope': u'local-machine', u'ad\
dresstype': u'ipv6', u'port': 17070, u'value': u'::1'}, {u'addresstype': u'ipv6', u'port': 17070, u'value': u'fe80:
2014/07/19-15:41:13 applied
stateServer
u'addresstype': u'ipv4', u'port': 17070, u'value': u'192.168.9.74'}, {u'networkscope': u'local-machine', u'addresstype': u'ipv4', u'port': 17070, u'value': u'127.0.0.1'}, {u'networkscope': u'local-machine', u'ad\
dresstype': u'ipv6', u'port': 17070, u'value': u'::1'}, {u'addresstype': u'ipv6', u'port': 17070, u'value': u'fe80:
we should not be writing to the database when there is no actual change.