The retry mechanism can be defeated by views that commit transactions halfway through
Bug #1412721 reported by
Raphaël Badin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Gavin Panella |
Bug Description
Th retry mechanism (retrying requests when they fail with serialization errors) doesn't deal well with views that commit transactions halfway through.
Let's say we have a view that does this:
Part A
Manual commit
Part B
If Part A fails with a serialization error, the entire request can be retried without problem. If the error happens in Part B, then the retry mechanism will also retry Part A which can be a problem.
We need to figure out a fix for this but one idea that comes to mind is this: store the information about Part A being done already and skip that part when retrying the view.
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Gavin Panella (allenap) |
Changed in maas: | |
milestone: | none → 1.8.0 |
Changed in maas: | |
status: | In Progress → Triaged |
Changed in maas: | |
milestone: | 1.8.0 → 1.9.0 |
no longer affects: | maas/1.8 |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.