2007-11-13 21:37:35 |
Christian Reis |
bug |
|
|
added bug |
2009-01-01 18:40:04 |
Curtis Hovey |
launchpad-registry: status |
New |
Triaged |
|
2009-01-01 18:40:04 |
Curtis Hovey |
launchpad-registry: importance |
Undecided |
Low |
|
2009-01-01 18:40:04 |
Curtis Hovey |
launchpad-registry: statusexplanation |
|
|
|
2009-04-29 01:52:34 |
Diogo Matsubara |
tags |
registry timeout |
registry-people timeout |
|
2009-04-29 01:52:59 |
Diogo Matsubara |
tags |
registry-people timeout |
chr registry-people timeout |
|
2009-05-25 05:42:15 |
Yasen Pramatarov |
removed subscriber Yasen Pramatarov |
|
|
|
2009-07-16 05:48:06 |
Stuart Bishop |
summary |
Merging people times out updating POSubmission and POMsgSet |
Person merging needs to be done asynchronously |
|
2009-07-16 05:48:06 |
Stuart Bishop |
description |
When merging two users on production, I ran into consistent timeouts on these two queries:
UPDATE POSubmission SET person=1457193 WHERE person=299986
(2218 rows)
UPDATE pomsgset SET reviewer=1457193 WHERE reviewer=299986
(1473 rows)
I'm wondering if the DB schema change that will be done to fix bug 30602 will address this. |
The Person merge code is robust but will timeout for records with lots of references to update.
The best way of addressing this is to queue merges to be done asyncronously.
This should be done for both user requested and admin merges. |
|
2009-07-16 05:48:25 |
Stuart Bishop |
description |
The Person merge code is robust but will timeout for records with lots of references to update.
The best way of addressing this is to queue merges to be done asyncronously.
This should be done for both user requested and admin merges. |
The Person merge code is robust but will timeout for records with lots of references to update.
The best way of addressing this is to queue merges to be done asynchronously.
This should be done for both user requested and admin merges. |
|
2009-10-16 03:11:25 |
Curtis Hovey |
tags |
chr registry-people timeout |
chr featire tech-debt timeout |
|
2009-10-16 03:11:37 |
Curtis Hovey |
tags |
chr featire tech-debt timeout |
chr feature tech-debt timeout |
|
2009-12-09 05:12:16 |
Curtis Hovey |
launchpad-registry: milestone |
|
series-3.1 |
|
2010-08-04 22:28:26 |
Curtis Hovey |
tags |
chr feature tech-debt timeout |
chr feature merge-deactivate tech-debt timeout |
|
2010-09-19 20:55:28 |
Robert Collins |
launchpad-registry: importance |
Low |
High |
|
2010-09-22 08:02:59 |
Steve McInerney |
bug |
|
|
added subscriber Canonical LOSAs |
2010-09-22 08:03:35 |
Steve McInerney |
tags |
chr feature merge-deactivate tech-debt timeout |
canonical-losa-lp chr feature merge-deactivate tech-debt timeout |
|
2010-10-07 23:12:45 |
Robert Collins |
summary |
Person merging needs to be done asynchronously |
Person:+delete timeouts : Person merging needs to be done asynchronously |
|
2010-10-14 04:52:24 |
Robert Collins |
tags |
canonical-losa-lp chr feature merge-deactivate tech-debt timeout |
canonical-losa-lp chr feature merge-deactivate pg83 tech-debt timeout |
|
2010-10-14 08:24:58 |
Stuart Bishop |
tags |
canonical-losa-lp chr feature merge-deactivate pg83 tech-debt timeout |
canonical-losa-lp chr feature merge-deactivate tech-debt timeout |
|
2011-01-12 17:03:07 |
Robert Collins |
launchpad: importance |
High |
Critical |
|
2011-02-15 15:48:21 |
Gavin Panella |
launchpad: assignee |
|
Gavin Panella (allenap) |
|
2011-02-23 11:05:24 |
Gavin Panella |
branch linked |
|
lp:~allenap/launchpad/async-person-merge-162510 |
|
2011-02-24 17:35:54 |
Gavin Panella |
launchpad: status |
Triaged |
In Progress |
|
2011-03-03 00:15:34 |
Launchpad QA Bot |
launchpad: milestone |
|
11.03 |
|
2011-03-03 00:15:37 |
Launchpad QA Bot |
tags |
canonical-losa-lp chr feature lp-registry merge-deactivate tech-debt timeout |
canonical-losa-lp chr feature lp-registry merge-deactivate qa-untestable tech-debt timeout |
|
2011-03-03 00:15:40 |
Launchpad QA Bot |
launchpad: status |
In Progress |
Fix Committed |
|
2011-03-03 14:25:07 |
Curtis Hovey |
description |
The Person merge code is robust but will timeout for records with lots of references to update.
The best way of addressing this is to queue merges to be done asynchronously.
This should be done for both user requested and admin merges. |
The Person merge code is robust but will timeout for records with lots of references to update.
The best way of addressing this is to queue merges to be done asynchronously.
This should be done for both user requested and admin merges.
See bug 728471 about the UI work needed to solve this issue. |
|
2011-03-10 16:43:59 |
Curtis Hovey |
launchpad: status |
Fix Committed |
Fix Released |
|
2011-03-10 18:07:30 |
Ahmed Shams |
removed subscriber Ahmed Shams |
|
|
|