A slave won't use the storage mountpoint
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql (Juju Charms Collection) |
Triaged
|
High
|
Unassigned |
Bug Description
A postgresql slave, when used with the storage broker charm and cinder volumes, did the following when coming up:
a) cloned the master
b) mounted the cinder volume
c) rsynced /var/lib/
d) started the slave but with data_directory set to /var/lib/
I think there are two bugs here:
a) it cloned the master before mounting the volume, therefore using the root filesystem. There might not be enough space there
b) it restarted the slave pointing at the original /var/lib directory instead of the new mount point
It could also be optimized to perhaps use the new mountpoint for the cloning in the first place, then it wouldn't need the rsync step.
We have this scenario live right now. Sorry for not attaching logs, I wanted to get this filed before EOD (and before my battery died, it's at 7% now!! :)