The task assignment algorithm considers the current value of shard_replication_factor rather than the value that was used to stage the data. This leads to unexpected side effects
Open
- Dominant language
- C
- Stars
- 12.8k
- Forks
- 794
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 31
Description
The task assignment algorithm considers the current value of shard_replication_factor rather than the value that was used to stage the data, which leads to unexpected side effects of setting shard_replication_factor at run-time. Investigate a solution.
Contributor guide
Research direction
Start by locating the task assignment algorithm and the code that stages data, then trace how shard_replication_factor is read in each path. Done means runtime changes no longer make task assignment use a different replication-factor value from the one used during staging, with the unexpected side effects covered by regression tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, postgresql
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100