Session/txn retries on sqlalchemy backend

Bug #1326608 reported by Joshua Harlow on 2014-06-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
taskflow
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.

Joshua Harlow (harlowja) wrote :

It should be relatively easy to plug-in a retry loop around/in https://github.com/openstack/taskflow/blob/master/taskflow/persistence/backends/impl_sqlalchemy.py#L299 (catching the appropriate exceptions and attempting the functor again...)

Changed in taskflow:
importance: Undecided → High
Joshua Harlow (harlowja) on 2014-12-04
Changed in taskflow:
status: New → Triaged
Joshua Harlow (harlowja) on 2014-12-19
Changed in taskflow:
milestone: none → next-kilo
assignee: nobody → Joshua Harlow (harlowja)
Joshua Harlow (harlowja) on 2015-01-29
Changed in taskflow:
assignee: Joshua Harlow (harlowja) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers