(Migrated) Can scheduled jobs invoked as a singleton?

(This message has been automatically imported from the retired mailing list)

Hi

It appears that scheduled services are invoked on all servers.

What would be the best strategy (ideally scheduler job config :wink: to only
invoke one instance of the service ?

Thanks

Tim

On 03/06/2015 00:36, Tim Hoffmn wrote:

It appears that scheduled services are invoked on all servers.

What would be the best strategy (ideally scheduler job config :wink: to
only invoke one instance of the service ?

You mean this?
https://github.com/zatosource/zato/issues/436

If so that was unintentional behaviour and it should be fixed in 2.0.4

On 03/06/15 01:36, Tim Hoffmn wrote:

It appears that scheduled services are invoked on all servers.

What would be the best strategy (ideally scheduler job config :wink: to only
invoke one instance of the service ?

Hi Tim,

are you looking for a way to invoke it on one selected server only?

Or you mean a service gets invoked simultaneously on each server each
time it’s triggered from the scheduler?

thanks,

When scheduled the Service is invoked on each server instance, so yes it
would be that bug.

It seemed that newly deployed schedules where only being invoked on a
single server, until such time as restarted the cluster, then all of the
scheduled jobs where invoked twice. (A bit embarrassing :wink:

Cheers

Tim

On 3 June 2015 at 15:46, B. Candler b.candler@pobox.com wrote:

On 03/06/2015 00:36, Tim Hoffmn wrote:

It appears that scheduled services are invoked on all servers.

What would be the best strategy (ideally scheduler job config :wink: to only
invoke one instance of the service ?

You mean this?
https://github.com/zatosource/zato/issues/436

If so that was unintentional behaviour and it should be fixed in 2.0.4