Merge lp:~edwin-grubbs/launchpad/bug-615654-registry-jobqueue-schema into lp:launchpad/db-devel
Proposed by
Edwin Grubbs
Status: | Merged |
---|---|
Merged at revision: | 9873 |
Proposed branch: | lp:~edwin-grubbs/launchpad/bug-615654-registry-jobqueue-schema |
Merge into: | lp:launchpad/db-devel |
Diff against target: |
78 lines (+45/-0) 3 files modified
database/schema/comments.sql (+16/-0) database/schema/patch-2208-99-0.sql (+27/-0) database/schema/security.cfg (+2/-0) |
To merge this branch: | bzr merge lp:~edwin-grubbs/launchpad/bug-615654-registry-jobqueue-schema |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stuart Bishop (community) | db | Approve | |
Robert Collins | db | Pending | |
Review via email: mp+35619@code.launchpad.net |
Description of the change
This branch adds the PersonTransferJob and QuestionJob tables.
The PersonTransferJob table will be used immediately to reduce or eliminate timeouts when adding lots of members to a team. In the future, the table will also be used for jobs where two person objects are merged.
The QuestionJob will be used to queue notifications about changes to the question object.
Should these jobs use new database users and have their own cronjobs? It seems like it would be much simpler to have a single cronjob run all the jobs.
To post a comment you must log in.
Quick thoughts:
- for question emails, perhaps a single 'emailjob' would be better, containing in it any email we want to send rather than question specific emails.
- PTJ seems sensible to me, though I thought we'd eliminated timeouts there already; could you link a recent oops for me to peruse (and its bug)? thanks.
- I don't see that we need new db users and cron jobs for this, though we do need one cronjob per queue AIUI today.