All workers run job when using sqlite3 data store

[legout]

Things to check first

• I have checked that my issue does not already have a solution in the FAQ

• I have searched the existing issues and didn't find my bug already reported there

• I have checked that my bug is still present in the latest release

Version

v4.0.0a5

What happened?

When using sqlite3 as the data store and redis as the event broker and having several workers running, jobs are executed by all workers.

How can we reproduce the bug?

job.py

def job(name, *args, **kwargs):
    print(name, args, kwargs)

scheduler.py

from apscheduler import Scheduler
from apscheduler.datastores.sqlalchemy import SQLAlchemyDataStore
from apscheduler.eventbrokers.redis import RedisEventBroker
from job import job

def main():
    data_store = SQLAlchemyDataStore(
        engine_or_url="sqlite+aiosqlite:////tmp/test.db"
    )
    event_broker = RedisEventBroker("redis://localhost:6379")

    with Scheduler(data_store, event_broker) as sched:
        sched.add_job(job, args=("job1", 1, 2, 3), kwargs=dict(a="A"))

if __name__ == "__main__":
    main()

worker.py

from apscheduler import Scheduler
from apscheduler.datastores.sqlalchemy import SQLAlchemyDataStore
from apscheduler.eventbrokers.redis import RedisEventBroker

def main():
    data_store = SQLAlchemyDataStore(
        engine_or_url="sqlite+aiosqlite:////tmp/test.db"
    )
    event_broker = RedisEventBroker("redis://localhost:6379")

    with Scheduler(data_store, event_broker) as sched:
        sched.run_until_stopped()

if __name__ == "__main__":
    main()

Here is a screenshot of running two workers and scheduling the job four times.

[agronholm]

Please try the code from master. There are boatloads of fixes there compared to v4.0.0a5.

[legout]

Thanks for the quick reply. I´ll give it a try!

[legout]

I´ve upgraded apscheduler to current master. The problem still exists.

Code works as expected, when switching from sqlite3 to postgres.

[agronholm]

For the record, sqlite3 is a pretty bad choice when you need concurrency. But this shouldn't be happening regardless, so I'll try to reproduce the problem locally and investigate.

[legout]

For sure. I´ll definitly use postgres in my production environment. But I´ve came across this bug during my testing. :-)

Thanks you very much for developing this fantastic lib.

[legout]

Hi @agronholm

are there already any updates?

Thanks

[agronholm]

Sorry, not yet. But rest assured I will look at this before the next release.