db and data are not persistence.
Bug #1130764 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charmworld |
Triaged
|
Low
|
Unassigned | ||
| mongodb (Juju Charms Collection) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Put db and maybe ingested branches on shared fs for persistence (./files?)
We are blocked by Bug #1088430
Related branches
lp:~rharding/charms/precise/mongodb/persistent_storage
- Juan L. Negron (community): Disapprove
-
Diff: 153 lines (+94/-3)4 files modifiedREADME.md (+15/-1)
config.yaml (+4/-0)
hooks/hooks.py (+74/-1)
revision (+1/-1)
| summary: |
- Put db and data on shared fs for persistence. + db and data are not persistence. |
| tags: | added: blocked |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| description: | updated |
| Changed in mongodb (Juju Charms Collection): | |
| status: | New → Fix Released |
To post a comment you must log in.
Rick abandoned a branch to solve this. There is an upstream bug that prevents the charm from declaring the mount point. The work around involved sshing into the mongodb unit, scanning dmesg for the next probable mount point, mounting the data at that point, then updating fstab. Rick was advised to not script this process out because it is possible for another process to use the mount point while the script is still running.