Scale APScheduler

[pola hema vishnu]

Hi,

I want to run multiple instances of APScheduler pointing to one common persistent job DB. Is it possible to run in that way?? I also mean that the jobs in the DB get shared among the Scheduler instances and at a point there is only one instance executing a scheduled job.

[Alex Grönholm]

Unfortunately no. I tried to make this happen with 2.0 but the operating
model I chose was fundamentally incompatible with the idea of running
multiple schedulers at once on the same DB. APScheduler 3.0 will have a
different operating model and I will be revisiting the possibility of
running multiple schedulers on a single job store. Not all backends will
be able to support this. SQAlchemy with pessimistic locking is my best
bet right now. MongoDB may also be able to support this, but I'll need
expert help with that. The Redis backend may go away entirely.
> --
> You received this message because you are subscribed to the Google
> Groups "APScheduler" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to apscheduler...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[pola hema vishnu]

What is the expected release of 3.0 ?

[Alex Grönholm]

19.11.2013 10:36, pola hema vishnu kirjoitti:

What is the expected release of 3.0 ?

The first half of 2014.

[Robson Peixoto]

News about this feature ?

[Alex Grönholm]

Depends on what you wish to achieve with this -- scalability or fault tolerance?

For more options, visit https://groups.google.com/d/optout.

[Robson Peixoto]

About scalability.

[Alex Grönholm]

I've been toying with the idea of adding an executor that can delegate work to workers in arbitrary locations. Would that satisfy your scaling needs?

[Robson Peixoto]

I need to run a lot of instances of the process in different nodes. But there are tasks that can only run one instance, but if I have more the one node it will have one running task for each node.

Are there a way to limit it?