Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md with CosmosDB workaround #1557

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1148,7 +1148,13 @@ be extremely useful in debugging certain issues and is encouraged.

#### "Multiple order-by items are not supported. Please specify a single order-by item."

When running Agenda on Azure cosmosDB, you might run into this issue caused by Agenda's sort query used for finding and locking the next job. To fix this, you can pass [custom sort option](#sortquery): `sort: { nextRunAt: 1 }`
When running Agenda on Azure CosmosDB, you might run into an issue caused by the Agenda sort query used for finding and locking the next job.

To fix this:
1. Create an index on the agendaJobs collection for sorting by nextRunAt and priority.
`db.collection('agendaJobs').createIndex({ nextRunAt: 1, priority: -1 }, { name: 'findAndLockNextJobIndex_sort' })`
2. Pass [custom sort option](#sortquery). For example:
`agenda.sort({ nextRunAt: 1, priority: -1 }).start()`

# Performance

Expand Down
Loading