temporalio / temporalio/temporal
timer_map collection in executions table can contains 10K's of entries
Open
Nobody has claimed this yet.
potential-bug
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Expected Behavior
It's suboptimal, I wonder if there's some bug that causes it.
Actual Behavior
Example from a customer running Temporal on ScyllaDB:
I don't know how it happened. Strangely, the partition key is a number, not a UUID. Maybe it's a hint?
Steps to Reproduce the Problem
Donno :(
Contributor guide
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 by locating the executions table and the timer_map persistence or update path, then inspect how timer entries and partition keys are generated for ScyllaDB. Compare the reported large collection with normal execution records and existing tests or diagnostics. Done means identifying a reproducible cause or clearly documenting why the collection grows and what should change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100