Backup to swift using wrong large object type
Bug #1489997 reported by
Matthew Van Dijk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
High
|
Matthew Van Dijk |
Bug Description
Backup to Swift should use Static Large Objects instead of the current Dynamic Large Objects.
A problem with DLO is that it relies on eventual consistency of container listing. This means that a restore could pull down an incomplete object.
SLO does not rely on eventual consistency. It can also provides significantly improved download performance.
Changed in trove: | |
assignee: | nobody → Matthew Van Dijk (mvandijk) |
Changed in trove: | |
milestone: | none → liberty-rc1 |
importance: | Undecided → High |
To post a comment you must log in.
I just had deja'vu when I read this bug.