Session/txn retries on sqlalchemy backend
Bug #1326608 reported by
Joshua Harlow
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| taskflow |
Triaged
|
High
|
Unassigned | ||
Bug Description
When a txn that was started with session.begin() conflicts with another ongoing txn we need to handle this failure (and remerge a new set of data) in the sqlalchemy backend (and repeat this X configurable number of times, then fail if we can not) to further avoid consistency issues.
Revision history for this message
| Joshua Harlow (harlowja) wrote | #1 |
| Changed in taskflow: | |
| importance: | Undecided → High |
| Changed in taskflow: | |
| status: | New → Triaged |
| Changed in taskflow: | |
| milestone: | none → next-kilo |
| assignee: | nobody → Joshua Harlow (harlowja) |
| Changed in taskflow: | |
| assignee: | Joshua Harlow (harlowja) → nobody |
To post a comment you must log in.
It should be relatively easy to plug-in a retry loop around/in https:/