Bug #52053 for AnyEvent-Gearman: no way to set unique ID for job

Tue Nov 24 22:06:48 2009 VKHERA [...] cpan.org - Ticket created

Subject:

no way to set unique ID for job

The C gearmand server requires the client specify a unique ID for each job (at least background jobs). There is no way with this module for the client to do so, making it impossible to submit more than one background job at a time.

Tue Nov 24 23:41:21 2009 typester [...] gmail.com - Correspondence added

On Tue Nov 24 22:06:48 2009, VKHERA wrote: Show quoted text

> The C gearmand server requires the client specify a unique ID for each > job (at least background > jobs). There is no way with this module for the client to do so, > making it impossible to submit > more than one background job at a time.

Try this: $gearman->add_task( $function => $workload, unique => 'unique_id_for_the_job', on_complete => sub { my $res = $_[1]; }, on_fail => sub { # job failed }, ); And I will mention about this in doc at next release. Thanks.

Tue Nov 24 23:41:22 2009 The RT System itself - Status changed from 'new' to 'open'

Tue Nov 24 23:41:23 2009 typester [...] gmail.com - Status changed from 'open' to 'resolved'

Wed Nov 25 10:17:00 2009 VKHERA [...] cpan.org - Correspondence added

On Tue Nov 24 23:41:21 2009, TYPESTER wrote: Show quoted text

> Try this: > > $gearman->add_task( > $function => $workload, > unique => 'unique_id_for_the_job', > on_complete => sub {

Wonderful. Now that I go back and re-read the Task.pm code, this becomes obvious :-) By the way, I'm comparing the various clients for perl, and this one is just as fast as the XS version to inject 10,000 jobs. Thanks for sharing your module.

Wed Nov 25 10:17:01 2009 The RT System itself - Status changed from 'resolved' to 'open'

Sun Jun 27 02:50:19 2010 melo [...] cpan.org - Taken