temporalio / temporalio/temporal
Validate num of matching task queue partition can be decreased
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Today, if operator need to increase number of task queue partitions, operator can simply increase both dynamic config to target number:
matching.numTaskqueueReadPartitions
matching.numTaskqueueWritePartitions
If operator need to decrease number of task queue partition, operator need to first decrease num of write partition, wait for all DB tasks to drain, then decrease num of read partitions
We need to validate the decrease scenario
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 tracing the dynamic-config handling for matching.numTaskqueueReadPartitions and matching.numTaskqueueWritePartitions. Review how partition changes are currently applied, then determine where the decrease sequence should be validated: reduce write partitions, wait for DB tasks to drain, and only then reduce read partitions. Done means the decrease scenario is validated without allowing an unsafe ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100