v7.2.1

Update Dependencies #452

v7.2.0

Resilience Updates (#450)

1. Move the act of poping a job off of a queue to a transaction via watch and multi.

   • This will have speed implications. In a busy system, the occurrences of trying to "pop" while writes are happening is high.
   • We may want to move to a LUA implementation to be truly blocking

2. Add queue.retryStuckJobs() which is a single method to retry jobs which have failed due to the worker timeout.

3. Add options.retryStuckJobs to the Scheduler, to automatically run the above queue.retryStuckJobs() periodically.

v7.1.0

Enhancements

• Add support for IORedis.Cluster type in ConnectionOptions for TypeScript (#438)
• JobLock option reEnqueue to skip trying job again (#449)

Docs

• mention side-effects of using wildcard queue (#421)
• Node Resque Interfaces: Queue, Worker, and Scheduler (486ce01)

Depreciations

• remove depreciated typo emitter (4bad5c9)

Misc

• replace declarations of var with const or let (#440)
• test against node v14 rather than v13 (#419)
• Update all dependencies to latest versions

v7.0.6

• Workers with wildcard queue will find new queues (#413)
• Update Dependencies

v7.0.5

• Multi worker cleanup (#346)
• Apply prettier to markdown files (#348)
• Add links to "domain" in documentation (#347)
• Fix checkWrapper typo (#345)
• Fix remaining typo (#377)
• Fix JavaScript mis-spelling typo (#370)
• Multiworker: fix error handler queue interpolation typo (#372)
• Update README.md (typo) (#361)
• Update dependencies

v7.0.4

connectionOptions.scanCount (#330)

Allows the setting of connectionOptions.scanCount to increase the number of keys scanned by each iteration of connection.getKeys. On large datasets, this will improve the performance of queue.allDelayed(), queue.locks(), queue.stats() and even scheduler polling can get very slow, taking over 30 seconds. This is because redis.scan() gets invoked hundreds of thousands of times when connection.getKeys() gets called. connection.getKeys() uses the SCAN command in Redis. When using SCAN, the COUNT parameter is set to 10 by default.

const connectionDetails = {
  host: "127.0.0.1",
  password: null,
  port: 6379,
  database: 0
  scanCount: 1000 // <-- New!
};

const queue = new Queue({ connection: connectionDetails }, jobs);
await queue.connect();
await queue.stats()

Misc

• Extend docker example to use typescript (#343)
• resque-web: support RAILS_RESQUE_REDIS env (#344)

v7.0.3

• update prettier and lint rules (#331)
• test node v13 and use redis v5 (#332)
• Remove jobs definition of producer example (#333)
• process.nextTick() takes callback as argument (#336)
• Code style fixes (#338)
• Update README.md (#339)
• update deps (#341)

v7.0.2

• Schedule should also watch delayed_queue_schedule #329
• Update Dependencies

v7.0.1

Update Dependencies

See fe629db

v7.0.0

Rename Master to Leader (#323)

While no underlying functionality has changed, this is a breaking change due to the new names of events/emitters

• Updated effected event handlers from master to leader
• Updated README.md to reflect the change from master to leader
• Any changes to import statements are them being reordered via TypeScript Hero
• Fixed typo in __tests__/utils/specHelper.ts, object was named SpecHeloer, changed to SpecHelper

Docker examples (#321)

• Adds examples of how to properly start and stop node-resque processes in docker.
• An accompanying blog post can be found here: https://blog.evantahler.com/production-node-applications-with-docker-3-devops-tips-for-shutting-down-properly-ed54f09f0a7f