TransactionRollbackError using the api to find users affected with dupes

Bug #535672 reported by Diogo Matsubara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Undecided
Unassigned

Bug Description

As seen on OOPS-1529EA966 a TransactionRollbackError: could not serialize access due to concurrent update was raised while calling users_affected_count_with_dupes() method of the bug model.

I wonder if this is a regression of bug 409907

Tags: api lp-bugs oops
description: updated
Revision history for this message
Stuart Bishop (stub) wrote :

A handful of database exceptions, including TransactionRollbackError, cause the request to be retried. This happens up to three times, at which point the exception is allowed to propagate.

We will see these rarely. If we see them more than we like, we need to increase the maximum retry count in the publisher to make them less likely. The probability of getting these exceptions will always be > 0.

Revision history for this message
Deryck Hodge (deryck) wrote :

stub, should I read what you're saying as "Won't Fix" or "wait and see?"

Revision history for this message
Stuart Bishop (stub) wrote :

WONT FIX until QA tell us it is a problem happening too frequently.

Changed in malone:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.