Trove replication verify volume size based on master
Bug #1357501 reported by
Iccha Sethi
This bug report is a duplicate of:
Bug #1359825: Trove replication slave values should default to master values.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Triaged
|
Medium
|
Peter Stachowski |
Bug Description
The slave should have minimum volume same as master. The reason why I think we should be doing this is -
the user builds master with a certain volume size because they expect it to grow atleast that much. so we should make sure the slave has volume size atleast as much as the master.
Changed in trove: | |
status: | New → Triaged |
Changed in trove: | |
importance: | Undecided → Medium |
milestone: | none → ongoing |
Changed in trove: | |
assignee: | nobody → Peter Stachowski (peterstac) |
summary: |
- Trove replication verify volume size based on master + Trove replication slave values should default to master values |
summary: |
- Trove replication slave values should default to master values + Trove replication verify volume size based on master |
To post a comment you must log in.
Space on the master is put to a variety of uses, including holding logs. Slaves don't need those logs, and so may not need as much space as the master.