Skip to content
Go to file

A MongoDB-based store for Quartz.

This is a MongoDB-backed job store for the Quartz scheduler.

Maven Artifacts

Artifacts are released to Bintray.

If you are using Maven, add the following repository definition to your pom.xml:


With Gradle, add the following to your build.gradle:

repositories {
    maven {
        url ""

The Most Recent Release

With Maven:


With Gradle:

compile "com.novemberain:quartz-mongodb:2.2.0-rc2"


Like most things in Quartz, this job store is configured via a property file,

# Use the MongoDB store
# MongoDB URI (optional if 'org.quartz.jobStore.addresses' is set)
# comma separated list of mongodb hosts/replica set seeds (optional if 'org.quartz.jobStore.mongoUri' is set)
# database name
# Will be used to create collections like mycol_jobs, mycol_triggers, mycol_calendars, mycol_locks
# thread count setting is ignored by the MongoDB store but Quartz requries it

Error Handling in Clustered Mode

When running in clustered mode, the store will periodically check in with the cluster. Should that operation fail, the store needs to decide what to do:

  • Shut down
  • Do nothing and optimistically proceed

Different strategies make sense in different scenarios. Pausing Quartz would be optimal but this job store currently doesn't have that option.

The org.quartz.jobStore.checkInErrorHandler.class property controls the error handler implementation.

To shut down the JVM (which is the default), add the following key to


to ignore the failure:


Clojure and Quartzite

If you use Quartzite or want your job classes to be available to Clojure code, use:


(this assumes Clojure jar is on classpath).

Job Data storage

By default you are allowed to pass any objects inside JobDataMap. It will be serialized and stored as a base64 string.

If your JobDataMap only contains simple types, it may be stored directly inside MongoDB to save some performance.



To enable clustering set the following property:

# turn clustering on:

# Must be unique for each node or AUTO to use autogenerated:
# org.quartz.scheduler.instanceId=node1

# The same cluster name on each node:

Each node in a cluster must have the same properties, except instanceId. To setup other clusters use different collection prefix:


Different time settings for cluster operations:

# Frequency (in milliseconds) at which this instance checks-in to cluster.
# Affects the rate of detecting failed instances.
# Defaults to 7500 ms.

# Time in millis after which a trigger can be considered as expired.
# Defaults to 10 minutes:

# Time in millis after which a job can be considered as expired.
# Defaults to 10 minutes:

# Time limit in millis after which a trigger should be treated as misfired.
# Defaults to 5000 ms.

# WriteConcern timeout in millis when writing in Replica Set.
# Defaults to 5000 ms.

Continuous Integration

Build Status

CI is hosted by Travis CI

Copyright & License

(c) Michael S. Klishin, Alex Petrov, 2011-2020.

Apache Public License 2.0


Project Origins

The project was originally started by MuleSoft. It supports all Quartz trigger types and tries to be as feature complete as possible.

Why the Fork?

MuleSoft developers did not respond to attempts to submit pull requests for several months. As more and more functionality was added and implementation code refactored, I decided to completely separate this fork form GitHub forks network because the project is now too different from the original one. All changes were made with respect to the Apache Public License 2.0.


A MongoDB-based store for the Quartz scheduler. This fork strives to be as feature complete as possible. Originally by MuleSoft.




You can’t perform that action at this time.