quantum-elixir / quantum-elixir/quantum-core
Startup with dynamic tasks problem
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 2.4k
- Forks
- 154
- Avg merge
- 2h 22m
- Merged PRs (30d)
- 3
Description
Hello, we encounter a problem when restarting our service that uses Quantum.
Context:
We have a service that loads dynamic jobs in at startup. We run this in Kubernetes on three pods. We implemented a custom storage backend that stores the jobs in Redis. These get loaded in at startup, however all the three pods execute the same jobs, only at startup, the future scheduled jobs only get executed once (as expected).
Is this a known issue? Maybe you can point us in the correct direction on how to solve this?
Maybe something like an on startup callback that announces to the other nodes that needs to sync data/state ?
Looking forward to your response(s)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Quantum's startup path for dynamically loaded jobs and the custom Redis storage backend, reproducing the behavior with three Kubernetes pods. Compare startup execution with later scheduled execution and determine what synchronization or ownership behavior is expected; done means the repeated startup execution is explained and a confirmed direction for resolving it is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, kubernetes, redis
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100