Increase replication timeouts for snapshot/restore
Bug #1362310 reported by
Morgan Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
High
|
Nikhil Manchanda |
Bug Description
In the current implementation, replication snapshots and creating a new slave from a snapshot may fail due to timeouts waiting for large amounts of data to be backed up or restored.
A potential solution is to somehow incorporate monitoring heartbeats from the guestagent to ensure that the operation can have as much time as necessary, without creating a situation where a failed guestagent will lock out the taskmanager. However, such a solution is beyond the scope of implementation for Juno.
As a temporary solution, change the timeouts on on the snapshot backup calls and the instance restore calls to effectively be "timeout = maxint".
Changed in trove: | |
assignee: | nobody → Morgan Jones (6-morgan) |
Changed in trove: | |
importance: | Undecided → High |
Changed in trove: | |
assignee: | Morgan Jones (6-morgan) → Nikhil Manchanda (slicknik) |
Changed in trove: | |
assignee: | Nikhil Manchanda (slicknik) → Morgan Jones (6-morgan) |
Changed in trove: | |
assignee: | Morgan Jones (6-morgan) → Nikhil Manchanda (slicknik) |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/121938
Review: https:/