launchpad-dev team mailing list archive

["Francis J. Lacoste" <francis.lacoste@xxxxxxxxxxxxx>]

On 12-05-24 12:59 AM, Aaron Bentley wrote:
> On 12-05-23 07:21 PM, Ian Booth wrote:
>> On 24/05/12 00:01, Aaron Bentley wrote:
>>> Only job classes that are mentioned in the 
>>> "jobs.celery.enabled_classes" feature flag will be run, so it is 
>>> safe to land your code.
> 
> 
>> Except that I haven't configured my new jobs to run via the normal
>> job runner so they will just queue up.
> 
> I suppose you could use lp.services.job.runner.celery_enabled to
> prevent your job from queueing up if they're not enabled to run via
> Celery.
> 
>> I may have to relent and configure my jobs to run via the normal
>> job runner until Celery is ready on production.
> 
> You are definitely on the bleeding edge, given that we haven't got
> Celery running jobs on production yet.  I do hope we'll be ready soon.
>  If you do want to run jobs via Cron, consider the run_jobs script.
> 

The deployment of celery to production is now blocked because celery
keeps long transaction open.

https://bugs.launchpad.net/launchpad/+bug/1003720

That needs fixing before we can proceed further.

Cheers

-- 
Francis J. Lacoste
francis.lacoste@xxxxxxxxxxxxx

Attachment: signature.asc
Description: OpenPGP digital signature