[Question] Job::save is safe to use for multiple instance or cluster?
Open
Discussion
Feature
need more info
- Dominant language
- JavaScript
- Stars
- 9.4k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Description
I saw this following line and increment ID and save operation is not atomic.
https://github.com/Automattic/kue/blob/master/lib/queue/job.js#L791
ID can conflict among shared instances. Is unique id safer than incremented id like old approach?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at lib/queue/job.js line 791 and trace Job::save's ID generation and save operation. Inspect how shared instances or cluster workers interact with Redis, then determine whether incremented IDs can collide and what behavior should count as resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, redis
- Domain
- backend, databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100