On Oct 5, 2012, at 10:07, Tom <[email protected]> wrote: > Unfortunately I'm afraid that I don't see how a scheduler can avoid the > concurrency problems. Note that the advantages (e.g. in availability) of > having a cluster should be maintained here, and so you cannot run a scheduler > in a separate process on a single server.
I would say if you want a task run *once* every five minutes, then you should run it on one server. If high availability is essential, perhaps you designate one primary server to run the task, and a backup server that monitors the primary server and takes over if the primary goes offline. > If every server would be running the scheduler, the same concurrency problems > would arise. I agree they would. What is this task you want to run every five minutes? Is there a way you could partition the work so that each server runs the script every five minutes and each server only does a specific fraction of the work? That would help distribute the workload as it increases, but wouldn't help a server goes offline. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
